+++ Hoylen Sue [Jan 02 15 14:17 ]:
I agree that avoiding hardcoding tag names is a worthy goal.
Clarification required
An HTML block would start with a line containing a single, unindented tag (either opening, closing, or self-closing), and would end, as before, with a blank line or end of document.
Can you please clarify if “containing a single” is supposed to mean:
a. containing only a single complete unindented tag (and nothing else);
b. containing only a single complete unindented tag or a partial unindented tag, but not both;
c. containing at least a single complete unindented tag;
d. containing either only a single partial unindented tag or least a single complete unindented tag; or both.
I was thinking (b). Of course, if we adopted Knagis’s suggestion, we’d
allow any number of complete tags and up to one incomplete tag, together
with whitespace.
Version 0.15 seems to be (d).
Version 0.15 does not implement any form of the proposal under
discussion here.
I prefer the options that allow for more than “only a single complete tag”, since there are situations where you want HTML tags to not contain any whitespace content.
I think we need to allow incomplete tags, since a long tag with many
attributes may be wrapped over several lines.
I don’t understand why, in example 1 of the 6th post,
<del>foo</del>
becomes<p><del>foo</del></p>
?
The proposal under discussion was that an HTML block starts with a line
containing a single tag (and no other non-whitespace content). This
line contains “foo” and another tag, so it doesn’t start an HTML block.
That means it is interpreted as a paragraph, and the tags in it are
read as inline HTML tags. See CommonMark Spec