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

Julian Reschke julian.reschke at gmx.de
Thu Feb 13 11:24:42 PST 2014


On 2014-02-13 18:28, Paul Hoffman wrote:
> 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>?

If you nest it into <linolabel> you end up with exactly the same amount 
of nesting as with my proposal.

Best regards, Julian



More information about the rfc-interest mailing list