25

When I edited an answer on Electrical Engineering Meta to add a second markdown table, both the first and second tables rendered correctly in preview, but the second table does not render. I've waited about 10 minutes in case there is some cache/refresh issue, and also tried both Chrome (87.0.4280.88 64-bit win10) and Firefox (84.0.1 64-bit win10) with equivalent result.

I think the actual problem is that the preview works even if there is no blank line before the table header row.

Simple table (looks good in preview) but no blank line before table header: | Question | Date Created | Date Closed | | -------- | ------------ | ----------- | | xxxxx | xxxxx | xxxxx | | xxxxx | xxxxx | xxxxx |

Simple table (looks good in preview) with blank line before table header:

Question Date Created Date Closed
xxxxx xxxxx xxxxx
xxxxx xxxxx xxxxx

Image of original table as seen in edit preview (correct):

as seen in edit preview

Image of original table as rendered in posted answer (incorrect):

as rendered in answer

Can it please be made so that the preview also doesn't render tables if there's no blank line between the table header and the line of text above it, so it matches the actual post rendering?

7
  • 1
    There needs to be an empty line above the table header. Currently there’s the line “These have been dealt with by adding additional tags:” directly above it. Jan 5, 2021 at 1:36
  • @user289905 want to make that an answer? I think you're right, I just now fixed up my original post. Leaving this here as a signpost for others.
    – MarkU
    Jan 5, 2021 at 1:39
  • 4
    This has already been reported here: New Feature: Table Support. Dang, @KodosJohnson beat me to it. Jan 5, 2021 at 1:40
  • 5
    Does this answer your question? Markdown preview doesn't match post Jan 5, 2021 at 2:13
  • 7
    @KodosJohnson Don't think that this is a duplicate of that. That one's a completely different bug, regarding line breaks after a table; this one is about line breaks before a table. While they may be the same cause, I'd leave those as two separate reports since they're two different bugs; if they turn out to be the same, an SE employee can close this. Jan 5, 2021 at 2:14
  • 1
    I just run into the same issue when composing the answer electronics.stackexchange.com/a/686067/101063. In case it matters was using Google Chome Version 118.0.5993.70 (Official Build) (64-bit) under Ubuntu 22.04.3 LTS. Oct 21, 2023 at 14:07
  • Asked 3 yrs 1 month ago. Still a problem today. I ran into the same issue [here]: (stats.stackexchange.com/questions/638886/…). Google Chrome Version 110.0.5481.78 (Official Build) (64-bit) on Win 10 Enterprise 1909 build 18363.2274.
    – CBRF23
    Feb 13 at 21:02

0

You must log in to answer this question.

Browse other questions tagged .