-
-
Notifications
You must be signed in to change notification settings - Fork 313
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
Void elements spec #436
base: master
Are you sure you want to change the base?
Void elements spec #436
Conversation
@jgm if this looks good to you, I'd be happy to put the changes together to |
There’s some more, mostly legacy elements: basefont, bgsound, command, frame, image, isindex, keygen, nextid listen in HTML, HTML4, and HTML5 (source), which may be useful to add? |
Thanks! Let's wait a little longer for comment (I've also +++ Yuki Izumi [Nov 07 16 00:13 ]:
|
I think another class of tags that should not start an HTML block is self-closing tags. |
I've started a discussion about self-closing tags and tags closed at the end of the same line that has the starts them here: https://talk.commonmark.org/t/reason-for-starting-an-html-block-when-the-closing-tag-is-on-the-same-line/2290/1 |
But the HTML block is not just about having content, but also about not being wrapped by Also the HTML blocks with all those start and end conditions are quite simplified and, as such, majority of the block contents does not really have to be valid HTML at all, so trying to interpret something of it more specially IMHO does not make much sense, unless you aim to specify the blocks into more details in other aspects too; e.g. by specifying how the whole block has to look like instead of just those start/end conditions. |
Void elements as described in the HTML spec should not start a CommonMark HTML block, because void elements cannot have any content.
The void elements are:
This updates the spec to account for void elements.
Refs #435