We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
So, it came to my attention that this:
> a blockquote # followed by an heading
gets parsed into something like:
<blockquote> <p>a blockquote</p> </blockquote> <h1>followed by an heading</h1>
Now, the spec states that you can be lazy and only put the > before the first line of a hard-wrapped paragraph. So the correct output should be:
<blockquote> <p>a blockquote</p> <h1>followed by an heading</h1> </blockquote>
In fact, github behaves like this (so does markdown.pl)
a blockquote
But other noteworthy implementations behave like showdown, such as:
So I'm a bit divided as if we should "fix it" or leave it as it is...
The text was updated successfully, but these errors were encountered:
Merge branch 'hotfix/#191' into develop
e754668
3df7062
Github behavior changed to match showdown original behavior.
This means:
is parsed as
foo
So this change will be reverted
Sorry, something went wrong.
several compliance fixes
aa12eab
Closes #191
tivie
No branches or pull requests
So, it came to my attention that this:
gets parsed into something like:
Now, the spec states that you can be lazy and only put the > before the first line of a hard-wrapped paragraph. So the correct output should be:
In fact, github behaves like this (so does markdown.pl)
followed by an heading
But other noteworthy implementations behave like showdown, such as:
So I'm a bit divided as if we should "fix it" or leave it as it is...
The text was updated successfully, but these errors were encountered: