Using <div> with inline HTML causes incorrect parsing about lowdown

[kristapsdz]

This is the default behaviour of the original Markdown specification. From pandoc(1):

     Original Markdown allows you to include HTML “blocks”: blocks of HTML
     between balanced tags that are separated from the surrounding text with
     blank lines, and start and end at the left margin.  Within these blocks,
     everything is interpreted as HTML, not Markdown; so (for example), * does
     not signify emphasis.

However, some renderers (including pandoc), extend this:

     Pandoc behaves this way when the markdown_strict format is used; but by
     default, pandoc interprets material between HTML block tags as Markdown.

Implementing something like this isn't easy, but it's not impossible: it would require breaking apart the text in a LOWDOWN_BLOCKHTML into a series of LOWDOWN_RAW_HTML separated by parsed markdown. If you'd like to take a look at this, it would require tokenising the interval of the block and calling the parser for non-HTML subintervals. See document.c where LOWDOWN_BLOCKHTML is pushed onto the parse stack.

[ron-at-swgy]

I understand, thank you. I may be able to do some CSS tricks with the "p" element to get a two-column layout on wider display ports in the interim. I'll close this issue.

[ron-at-swgy]

Kristaps, I'm don't understand the difference between node types LOWDOWN_BLOCKHTML and LOWDOWN_RAW_HTML. Would it make sense to parse my case into a few LOWDOWN_BLOCKHTML nodes with other markdown nodes in between? I see that <hr /> and <br /> are parsed as LOWDOWN_BLOCKHTML. When would I expect to see LOWDOWN_RAW_HTML?

Thank you,
Ron

[ron-at-swgy]

Addressed in #128