You removed a following sentence:
If a line containing a single -
can be interpreted as an
empty [list items], it should be interpreted this way
and not as a [setext heading underline].
Ok. Now I need your clarification on the following cases.
* Text
-
Text
you do:
<ul>
<li>
<h2>Text</h2>
Text</li>
</ul>
And:
- List
text
-
<ul>
<li>List
text</li>
<li></li>
</ul>
What is it? Why it’s so?
You shouldn’t have deleted this sentence.
As I remember you had problems in implementation of CommonMark 0.30 with empty list items, and as I guess you just decided to solve your algorithmic problems by human words. Lol, it’s a bad idea.
- List
text
-
There is no such thing as a lazy settext header. Only paragraphs can be lazy.
Consider two other, similar situations: lazy continuations that end with a single equal sign (that look like a level 1 settext header) and lazy continuations that end with a single -
coming out of a quote block instead of a list.
- List
text
=
> quote
text
-
> quote
text
=
dingus link
None of these are settext headers. The ones with a -
form lists, but the ones with =
are just text, not headers, so there’s no ambiguity here.
Ok. I agree with above examples about lazy paragraphs, but:
* Text
-
Text
Why here I should consider second list item as a setext heading?
Ok, guys, you decided so, let it be so, and doesn’t matter why. Stop considering this topic.
https://spec.commonmark.org/0.31.2/#list-items
- When the first list item in a list interrupts a paragraph—that is, when it starts on a line that would otherwise count as paragraph continuation text—then (a) the lines Ls must not begin with a blank line, and (b) if the list item is ordered, the start number must be 1.