This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 10170 - I really think it should be possible to nest the ul and ol elements using normal tag standard. whey not make it possible to nest it by allowing ul/ol inside other ul/ol tags, just like any other li elements?
Summary: I really think it should be possible to nest the ul and ol elements using nor...
Status: RESOLVED WONTFIX
Alias: None
Product: HTML WG
Classification: Unclassified
Component: pre-LC1 HTML5 spec (editor: Ian Hickson) (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: ---
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-07-15 11:16 UTC by contributor
Modified: 2010-10-04 14:47 UTC (History)
4 users (show)

See Also:

Attachments

Description contributor 2010-07-15 11:16:17 UTC 
Section: http://www.whatwg.org/specs/web-apps/current-work/#the-ul-element

Comment:
I really think it should be possible to nest the ul and ol elements using
normal tag standard. whey not make it possible to nest it by allowing ul/ol
inside other ul/ol tags, just like any other li elements?

Posted from: 62.119.132.30
Comment 1 Ian 'Hixie' Hickson 2010-09-08 00:43:32 UTC 
What would it mean?

An <ol> is a list of items. An <li> is an item. An <ol> isn't an item.

If you do:

    <ol>
      <li>...A...</li>
      <ol>
        <li>...B...</li>
      </ol>
      <li>...C...</li>
    </ol>

...then what is B? What is the second item of the outer list?

EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document:
   http://dev.w3.org/html5/decision-policy/decision-policy.html

Status: Rejected
Change Description: no spec change
Rationale: I don't understand the semantics of the proposal.