[whatwg] Interpretation issue: can <section> be used for "extended paragraphs"?

Markus Ernst derernst at gmx.ch
Tue Jun 14 02:04:16 PDT 2011

Am 14.06.2011 09:32 schrieb Ian Hickson:
> On Fri, 11 Mar 2011, Markus Ernst wrote:
>> Instead of a new paragraph concept, there could also be a new concept
>> for inline (resp. Phrasing Content) lists. The concept is actually not
>> too new - for quotes, e.g., we've had both block level<blockquote>  and
>> an inline level<q>  elements for long. Why not the same for lists?
>> Consider this markup of Andy's use case:
>> <p>I always like to eat these cheeses:
>> <il>
>>   <ili>Cheddar</ili>,
>>   <ili>Stilton</ili>, and
>>   <ili>Red Lester</ili>,
>> </il>
>> but I enjoy them most with one of these biscuits:
>> <il>
>>   <ili>wheat crackers</ili>,
>>   <ili>rye crackers</ili>,
>>   <ili>digestives</ili>,
>> </il>
>> and some chutney.</p>
>> <il>  stands for "inline list",<ili>  for "inline list item" (it's a pity
>> we can't reuse<li>  for BC reasons). Conforming UAs would be required to
>> ignore any content in an<il>  element, except it is in an<ili>  element.
>> Like that, the above example would be perfectly readable in legacy UAs,
>> but make sense in HTML5-capable UAs.
>> It would even be easy to stlye the output for legacy UAs supporting
>> display:list-item, as this example illustrates:
>> http://www.markusernst.ch/stuff_for_the_world/list-test.html
> What problem does this solve?

It solves the first use case Jukka mentioned in his original post:

Am 10.03.2011 09:20 schrieb Jukka K. Korpela:
 > The <p> element (ever since it became an element) has always allowed
 > inline (text-level) content only, and no change is planned to this in
 > HTML5. Under these circumstances, what should we say to people to
 > need to use paragraphs that contain lists, for example?

More information about the whatwg mailing list