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
(each observed flaw, all related, is marked with 🚩)
🚩 Normalize tries to make pretty, indented HTML, but in so doing messes up the whitespace of <pre> blocks which should never be touched:
If Normalize is unchecked, you can see the untouched HTML output of the various Markdown parsers.
🚩 Note how the preview rendering uses the normalized version. Even if Normalize had no bugs, it would be best if the preview displayed the actual HTML shown above it.
CommonMark Dingus just for comparison:
🚩 The same problem occurs for non-pre <code> bocks used for inline code:
Normalize is unchecked shows the correct HTML, 🚩 but as before the preview rendering uses the faulty normalized version:
CommonMark Dingus for comparison:
The text was updated successfully, but these errors were encountered:
BTW, I'm the author of htmlnorm, a Javascript HTML normalizer. It emphasizes safety / semantic fidelity, in case you want to try doing this on the client side, paying particular attention to HTML5 spec and the whitespace rules it imposes on browser interpretation of HTML.
(each observed flaw, all related, is marked with 🚩)
🚩 Normalize tries to make pretty, indented HTML, but in so doing messes up the whitespace of
<pre>
blocks which should never be touched:If Normalize is unchecked, you can see the untouched HTML output of the various Markdown parsers.
🚩 Note how the preview rendering uses the normalized version. Even if Normalize had no bugs, it would be best if the preview displayed the actual HTML shown above it.
CommonMark Dingus just for comparison:
🚩 The same problem occurs for non-pre
<code>
bocks used for inline code:Normalize is unchecked shows the correct HTML, 🚩 but as before the preview rendering uses the faulty normalized version:
CommonMark Dingus for comparison:
The text was updated successfully, but these errors were encountered: