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
New (?) bug rendering divs next to paragraphs? #220
Comments
Examples 4 and 6 have to fail because the Example 7 should not fail. It is similar to 5 which is parsed correctly. So this has to do with the attribute probably. |
I have found the problem and this will be fixed in the next release. Please also note that when using "parse_block_html" that the closing tag needs to be on a separate line! |
Thanks! Confused about the Indeed, these examples were converted correctly (as a paragraph followed by a |
Okay, I will use |
kramdown has functioned this way since 2009, so this is not new behaviour. However, if you can find an example where kramdown acted differently, please share it! |
My mistake! Apparently it's the behavior of other renderers (github, for example), and I got confused. |
No problem :) Thank you for reporting! |
I just noticed (while chasing down a new Nokogiri bug) that a bunch of old blog posts are not rendering correctly. There are two symptoms, apparently:
<div>
that appears without a newline right before it is not recognized, and comes out HTML escaped inside its surrounding block<div>
with any attribute at all is not recognized unless it is preceded by TWO newlinesHere's a gist showing the behavior
Amusingly, github parses the source correctly. View "RAW" to see the problem.
The text was updated successfully, but these errors were encountered: