[rfc-i] Supporting both ease-of-entry and un-labeled list items in v3

Paul Hoffman paul.hoffman at vpnc.org
Thu Feb 13 09:28:36 PST 2014

On Feb 13, 2014, at 9:12 AM, Julian Reschke <julian.reschke at gmx.de> wrote:

>> A possible third alternative, which makes me cringe a bit but I can see some logic to it, would be:
>>    <list style="symbols">
>>       <li>This is the first element with a bullet.</li>
>>       <li>This is the second element with a bullet.
>>       <linolabel>This is part of the second element,
>>          but it does not have a bullet.</linolabel>
>>       <li>This is the third element with a bullet.</li>
>>    </list>
>> That solves your "not mixing block-level elements with text content" problem and still would not force people to have to use two elements everywhere. Thoughts?
> It  doesn't help if a list item needs to contain, for instance, a text paragraph and a preformatted example (for which we don't have an element yet).

Why is that? Assuming that we add an element for preformatted example, why could that not allowed in both <li> and <linolabel>?

--Paul Hoffman

More information about the rfc-interest mailing list