Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

Markdown: HTML parsing issues when content isn't ended with a blank line #216

aahan opened this Issue Feb 14, 2014 · 2 comments


None yet
4 participants

aahan commented Feb 14, 2014

Sample content for testing: https://gist.github.com/anonymous/0c330b866c0768eb38fa

If there's no blank line after the sample content (above), the output looks like this:


HTML of the broken content looks like this:

<p>p><em>Please note that by continuing to use the site, you are agreeing to all our aforementioned policies.</em></p>

The fix is to add an empty line after the content. But why is this necessary? Is this intended, or should this be considered a bug?

mattwiebe added a commit to mattwiebe/Jetpack that referenced this issue Mar 12, 2014

Handle unpredictable para choking in Markdown Extra
Doesn't happen consistently on all systems. Still, an easy fix once identified.

Fixes #216

@jeherve jeherve added this to the 3.0 Freeze milestone Mar 13, 2014

mattwiebe added a commit that referenced this issue Mar 13, 2014

Markdown: fix for bizarre para mangling by Markdown Extra.
Wasn't able to duplicate locally, but could on sandbox. Big edge case but that's software.

See #216

Merges r93595-wpcom.

mattwiebe commented Mar 14, 2014

This was fixed by b1447d0 - I used "see" instead of "fixes" in the commit.

@mattwiebe mattwiebe closed this Mar 14, 2014

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment