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 11903 - i think it'd be more convenient if explicit sections could be children of implicit sections, so you can use implicit sections in general and throw in an <aside> somewhere without breaking the outline. now if you want to throw in an <aside>, you need to ch
Summary: i think it'd be more convenient if explicit sections could be children of imp...
Status: RESOLVED WONTFIX
Alias: None
Product: HTML WG
Classification: Unclassified
Component: LC1 HTML5 spec (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: 2011-01-28 11:01 UTC by contributor
Modified: 2012-01-23 09:58 UTC (History)
6 users (show)

See Also:

Attachments

Description contributor 2011-01-28 11:01:20 UTC 
Specification: http://www.whatwg.org/specs/web-apps/current-work/complete/sections.html
Section: http://www.whatwg.org/specs/web-apps/current-work/#outlines

Comment:
i think it'd be more convenient if explicit sections could be children of
implicit sections, so you can use implicit sections in general and throw in an
<aside> somewhere without breaking the outline. now if you want to throw in an
<aside>, you need to change everything to also throw in explicit <section>s
everywhere just to make the outline as it was before throwing in the <aside>

Posted from: 85.227.154.141 by simonp@opera.com
Comment 1 Ian 'Hixie' Hickson 2011-02-18 23:52:12 UTC 
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: The problem is that if you do that then it becomes essentially impossible to automatically style <h1>, and any other manipulation of sections that relies on the DOM and skips out on implementing the (rather complex) outline algorithm can't even get the basics right.

I agree that it is problematic when you mix the two models at a sibling level. Not sure what can be done about that.
Comment 2 Michael[tm] Smith 2011-08-04 05:15:51 UTC 
mass-move component to LC1