4 ms·
Hmmm, interesting. So that's going in the other direction to the HTML5 spec, in which you considered a header in relation to the section it's contained in, with
by blowski 14y ago
Hmmm, interesting. So that's going in the other direction to the HTML5 spec, in which you considered a header in relation to the section it's contained in, without worrying about the section's relation to the whole document. It was the browser's job to do the latter.
I will keep an eye on this. Thanks for the pointer.
- j4_james 14y agoIn case you're interested, this is the bug report that resulted in the change: https://www.w3.org/Bugs/Public/show_bug.cgi?id=19741 https://www.w3.org/Bugs/Public/show_bug.cgi?id=19741 The final editor's response explains the reasoning: "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"
- blowski 14y agoThanks for that. I had assumed the header structures was one of the more stable parts of the spec!