-
Notifications
You must be signed in to change notification settings - Fork 385
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Markdown incorrectly processing HTML #134
Comments
Any update on this one? |
For the record: this isn't a bug, it's a consequence of how Sundown looks for the ending tag. In order to tell Sundown where your tag really ends, you should indent the HTML, or at least the first
|
Good to know about the workaround. But from the perspective of the library user, I'd consider this a bug as valid markdown input is producing invalid html output. Shouldn't Sundown just not process markdown inside HTML tags instead of relying on indentation? According to the Markdown spec:
|
Well, that's actually from the spec. The spec says the ending tag should be on an unindented line, and be followed by empty lines. So, Sundown searches for the first |
Don't use "for (declaration"
Not sure if this is another bug that popped up after the fix for issue #96, but looks like I found another bug in processing inline HTML. The following HTML snippet reproduces the bug:
generates:
Notice that an extra
<p>
tag is generated before the<h2>
tag and after the last</div>
tag, resulting in an invalid HTML.The text was updated successfully, but these errors were encountered: