<button> is both and neither a block and a span element

[morandat]

< button > tags are almost always expanded as text (sorry I can't anymore figure out the only case where there are well interpreted).

It comes from the fact that button is both in HTML_SPAN_ELEMENTS/HTML_BLOCK_ELEMENTS and in HTML_CONTENT_MODEL_SPAN/HTML_CONTENT_MODEL_BLOCK.
Removing button from HTML_BLOCK_ELEMENTS seems to fix everything ... but I'm not sure about all side-effects.

[gettalong]

Thanks for the input! I will have to do some research before changing this - does anybody else have experience with this stuff?

[gettalong]

@morandat Do you have a test case for this? I.e. what doesn't work for you?

[morandat]

@gettalong It's not minimal, but close to. It's actually supposed to render some bootstrappy thing.

https://gist.github.com/morandat/64031638f916b2e0a1c6

[gettalong]

@morandat Okay, but what is the input and what is the output?

[gettalong]

If I take the gist as input, the <button> element is rendered incorrectly - this is fixed with your proposed change.

Note that the second <div>...</div> block is not valid in kramdown as the closing tag needs to be on a separate line.

[morandat]

Yep, the button tag is rendered incorrectly ...
Yep sorry, I wrote the example very quickly.

[gettalong]

Thanks for your input and the report, this is fixed now with commit d656641!

Just one note: If possible, only open a pull request if you already have code that corrects a bug, this avoids having two open issues with the same problem.