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
I think commonmark.js has a bug here, because the __ in __! is a left-flanking delimiter run. It is followed by a unicode punctuation character (!), and it is preceded by the beginning of the line (which is treated as whitespace).
More generally, it seems like, if the second example parses successfully, then the first one must also parse. The spec says that underscores are allowed in the middle of underscore-delimited strong emphasis (it wouldn't be allowed at the beginning or end of the emphasis span, but it's not).
Consider these three example snippets:
And the results they give in the commonmark dingus:
I think commonmark.js has a bug here, because the
__
in__!
is a left-flanking delimiter run. It is followed by a unicode punctuation character (!
), and it is preceded by the beginning of the line (which is treated as whitespace).More generally, it seems like, if the second example parses successfully, then the first one must also parse. The spec says that underscores are allowed in the middle of underscore-delimited strong emphasis (it wouldn't be allowed at the beginning or end of the emphasis span, but it's not).
This example was found by differential fuzzing with pulldown-cmark. Corresponding issue: pulldown-cmark/pulldown-cmark#660
The text was updated successfully, but these errors were encountered: