[html5] Using <section> and <h1> ? Theoretical?

Andrew J Roazen Andrew.Roazen at nau.edu
Fri May 16 13:14:09 PDT 2014

On May 15, 2014, at 2:28 PM, Micky Hulse <mickyhulse.lists at gmail.com<mailto:mickyhulse.lists at gmail.com>> wrote:

Interesting idea. I think I get it.

If I understand correctly, it kinda (maybe just a little bit) reminds me of how I handle the styling of headings using CSS class names (in an HTML5 <section>/<h1>,<h2>, etc. context):

<h1 class="h6">This is an H1 that's styled like an H6</h1>

As I understand it, <section> being a purely semantic and nonpresentational element is most likely aimed at parsers rather than people. A parser can be expected to consume a section, detect the topmost level heading in it and renumber the headers accordingly. Considering the likelihood that a parser will already be transforming the contents into a native data structure, this isn't onerous.

I only suggested the attribute as a compromise, but really this shouldn't be necessary unless there's a developer need for overriding a default here.

Until there's a use case scenario for a browser needing to have multiple top level headers, then <section> should know its place in a document as a purely semantic wrapper, and outlining should continue to behave as though the contents were part of a whole (because they are).

Don't shift a paradigm for an edge case need.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.whatwg.org/pipermail/help-whatwg.org/attachments/20140516/0b33a268/attachment.htm>

More information about the Help mailing list