You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
One observation: if you change the setext heading line regex to something that will never be matched, the empty p tag disappears. So this is due to some interference with setext heading parsing.
Similar to what you note, I think the area around definitions/setext headings/lists is very hard to think about. One example: wooorm/markdown-rs#22 (comment). I have no idea what should happen in these cases. Which comes first? Which construct has precedence, and what happens if it doesn’t match
I think this is a bug in
commonmark.js
:On the dingus, it yields:
Rendered here (
cmark-gfm
+ more GH stuff, likely same as justcmark
):---
===
<p></p>
should show up, that’s a clear bug.<p>---</p>
makes more sense here, as definitions/paragraphs/setext heading underlines interplay weirdly (Mention that link reference definitions are constructed from paragraphs commonmark-spec#605).The text was updated successfully, but these errors were encountered: