This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
http://www.whatwg.org/specs/web-apps/current-work/#sectioning-content-0 The draft currently defines "sectioning content" as "content that defines the scope of headings, footers, and contact information". That seems to omit from the definition the <section> element itself, as well as the <nav>, <article>, and <aside> elements.
I removed the bit about contact information, does that solve the problem?
I still don't think "Sectioning content is content that defines the scope of headings and footers." is going to be clear to most readers. Perhaps explicitly mentioning some elements names would help: "Sectioning content is content that defines the scope of headings and footers. The contents of the <section>, <article>, <nav> and <aside> elements constitute sectioning content." or maybe: "The contents of the <section>, <article>, <nav> and <aside> elements constitute sectioning content. The scope of a particular heading or footer is defined by the <section>, <article>, <nav> or <aside> element that contains that heading or footer."
I have a separate issue logged about making sure all the content model definitions list all the elements that fall into that content model; it's scheduled for August or something (so that I don't have to keep doing it when we change things).
This bug predates the HTML Working Group Decision Policy. If you are satisfied with the resolution of this bug, 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 This bug is now being moved to VERIFIED. Please respond within two weeks. If this bug is not closed, reopened or escalated within two weeks, it may be marked as NoReply and will no longer be considered a pending comment.