This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
in http://dev.w3.org/html5/spec/headings-and-sections.html#headings-and-sections there is a non-normative statement suggesting authors prefer the use of sections and repeated h1 elements over the use of the odler numbered headings. This is in conflict with the statement at the end of http://dev.w3.org/html5/spec/the-aside-element.html#the-h1,-h2,-h3,-h4,-h5,-and-h6-elements that authors should choose what suits them. It is clearly bad advice in the absence of the outline algorithm working, and even were that widely implemented it breaks backward compatibility. It is not clear that the value of this advice justifies this cost in theory, and it is clear that in the current situation there is little value and high cost.
*** Bug 19742 has been marked as a duplicate of this bug. ***
The two pieces of advice mentioned above don't contradict each other. You can use <section> with legacy <h2>-<h6> elements fine.
(In reply to comment #0) > in > http://dev.w3.org/html5/spec/headings-and-sections.html#headings-and- > sections there is a non-normative statement suggesting authors prefer the > use of sections and repeated h1 elements over the use of the odler numbered > headings. > > This is in conflict with the statement at the end of > http://dev.w3.org/html5/spec/the-aside-element.html#the-h1,-h2,-h3,-h4,-h5,- > and-h6-elements that authors should choose what suits them. > > It is clearly bad advice in the absence of the outline algorithm working, > and even were that widely implemented it breaks backward compatibility. > > It is not clear that the value of this advice justifies this cost in theory, > and it is clear that in the current situation there is little value and high > cost. The advice: "Sections may contain headings of any rank, but authors are strongly encouraged to either use only h1 elements, or to use elements of the appropriate rank for the section's nesting level." needs to be removed, as it is recommends authoring for non existent consumers and breaks structural semantics for existing consumers, suggest this text instaed: "Sections may contain headings of any rank, but authors are strongly encouraged to use elements of the appropriate rank for the section's nesting level."
(In reply to comment #2) > The two pieces of advice mentioned above don't contradict each other. You > can use <section> with legacy <h2>-<h6> elements fine. Whether the the 2 pieces of advice is contradictory or not is irrelevant, the issue is that the advice is bad advice and should be removed. The advice does not reflect the current, histroical or practical future reality of best practice for coding heading structures.
The sentence you quote is just saying not to use both.
(In reply to comment #5) > The sentence you quote is just saying not to use both. yeah you are right , have been misreading it all along. makes little difference to suggestion to change it though, as it appears confusing to more than just me, and the spec should advise aganst using just <h1>'s for previously stated reasons.
(In reply to comment #5) > The sentence you quote is just saying not to use both. No, "...authors are strongly encouraged to either use only h1 elements, or..." says that just using h1 is one of the recommended options. It should not be recommended. The requested fix is to remove the text "either use only h1 elements, or".
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: Accepted Change removed advice recommending use of h1 elements as the utline algorithm has virtually no implementations and as a result use of h1 elements flattens document outlines for users who actually consume the heading semantics. While use of elements of the appropriate rank for the section's nesting level is backwards compatible Rationale: agreed with comment 1.
commit for bug resolution https://github.com/w3c/html/commit/556da56c44a2be0cabb9eccbe51fe583fcdf4332