Also, this header row style is inconsistent with markdown syntax where bold items are surrounded by **asterisks**. See this related thread where you all decided to remove the strikethrough for the checkbox style.
We’re still thinking about this, the Markdown format is explicitly marking the first row as a header, so the new behaviour is the correct/standard one, BUT I understand your point and that’s why we didn’t had it in the first iteration.
We don’t have a solution right now, but we’re brainstorming on it
Instead of automatically bolding the top row and treating it as a header, it would be nice to be able to selectively treat rows and columns as headers, adding and removing ** asterisks as necessary to be consistent with the Markdown markup. Here’s an example of a typical table for me:
I agree, I feel like if a table needs a table header row, it should be an option to add one when clicking the three-dot menu for the table (or when writing in pure markdown). The HTML output neither defines the top row as being contained within a <thead>, nor the cells as <th>, they resemble every other row as <tr> and <td>'s, meaning that sharing using copy as html option won’t correctly translate in another program. the markdown copy does follow standard markdown correctly but assumes that the first row is always a header. copying and pasting a markdown table that has no header row from a markdown file does not translate into a table in Panda.
Pardon if this is not possible due to Markdown’s restrictions, but it would be nice to use Heading levels in Table Headers. It’s a bit odd that this is disabled in the Alpha. Maybe this changed in the Beta?