W3C home > Mailing lists > Public > public-html@w3.org > August 2009

Re: Proposal: <content> element

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Mon, 17 Aug 2009 09:21:27 -0500
Message-ID: <dd0fbad0908170721y692dea71x70360dfbbb649967@mail.gmail.com>
To: Steven Faulkner <faulkner.steve@gmail.com>
Cc: Anne van Kesteren <annevk@opera.com>, HTML WG <public-html@w3.org>
On Mon, Aug 17, 2009 at 4:58 AM, Steven
Faulkner<faulkner.steve@gmail.com> wrote:
> hi anne,
> I agree, a problem i see with inferring things from the google stats is that
> there is no indication of how often a class name is used on a page, also
> what are the relative uses of these or similar values as id values?
> if it is most often used singularly in the examples of
> header/footer/content, this would indicate that allowing multiple instances
> of these elements on a page, is not supported by the (unavailable) data.

So it looks like the main problem here is determining whether we're
asking for a counterpart to <header>/<footer>/<aside> and such
(without the implicit sectioning), or if we're asking for a
language-blessed replacement for #main.

I'm not sure if the former is useful.  For the latter, I basically
treat <article> as being that element.  It's not always going to be
such (you can have multiple <article>s on a page), but if an AT is
trying to skip down to something useful, skipping to the first
<article> would be a good start.

~TJ
Received on Monday, 17 August 2009 14:22:29 UTC

This archive was generated by hypermail 2.3.1 : Monday, 29 September 2014 09:39:06 UTC