W3C home > Mailing lists > Public > public-html@w3.org > February 2013

Re: Context of the main element

From: Jeremy Keith <jeremy@adactio.com>
Date: Fri, 1 Feb 2013 11:20:21 +0000
Cc: Gez Lemon <g.lemon@webprofession.com>, "HTML WG (public-html@w3.org)" <public-html@w3.org>
Message-Id: <25809EEA-0647-48FC-875E-C551FFE164F1@adactio.com>
To: Steve Faulkner <faulkner.steve@gmail.com>
Steve wrote:
> for example I don't see how your suggested changes will benefit users who consume the semantics, what will the semantics of nested main be when mapped to the acc layer?

Oh, none. I would imagine that any instances of the main element that don't correspond to the main landmark (i.e. any instances that aren't scoped to the document body) wouldn't have any special semantics for the acc layer …they'd effectively be no different than divs.

And that prompts the question "well, why not just use a div, then?" …which is a fair question. But seeing as HTML5 introduces a few other new elements that (I believe) don't have any effect on the outline or on the acc layer (e.g. header and footer within sectioning content), then the introduction of a new element like main seems like a good opportunity to give authors the option of using a dedicated element in place of a generic div.

Cameron referred to this as "semantic sugar", which, while it was probably meant as a negative term, is actually a pretty good way of describe many of the new elements in HTML5.

So my suggestion really just boils down to throwing a bone to authors.

As for use cases: every single use of a header or footer within sectioning content (other than the body element) is also a potential use case for main.


Jeremy Keith

a d a c t i o

Received on Friday, 1 February 2013 19:25:48 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 29 October 2015 10:16:31 UTC