W3C home > Mailing lists > Public > public-html@w3.org > April 2016

Re: Always use h1-h6 by level again

From: Geoffrey Sneddon <me@gsnedders.com>
Date: Tue, 19 Apr 2016 04:02:23 +0100
Message-ID: <CAHKdfMhy+3mP9z_Bw9Rvi+P6P4YXcE8Wg-zOjAvfaJ-XoYv27w@mail.gmail.com>
To: John Foliot <john.foliot@deque.com>
Cc: Chaals McCathie Nevile <chaals@yandex-team.ru>, "White, Jason J" <jjwhite@ets.org>, Alastair Campbell <acampbell@nomensa.com>, HTML WG <public-html@w3.org>
On Mon, Apr 18, 2016 at 4:21 PM, John Foliot <john.foliot@deque.com> wrote:
> 1) Should we withdraw the "magic heuristic outline" proposal from HTML5 that has not been implemented?
>         Yes, 100% support
> 2) Should we contemplate pursing a new <h> element that would pursue this nesting idea slightly differently (closer to the XHTML2 model)?
>         I would support that effort, yes. It would be interesting to pursue the stateless Heading element, but I fear we may not get support from the browser vendors, but it would be worth the ask.

Given it's so slightly different, I wonder if there's any more chance
of it getting implementation support. Do we have any evidence that
implementations are more likely to support
<section><h/><section><h/></section></section> than they are to
support <section><h1/><section><h1/></section></section>? As far as I
can see there is nothing to suggest implementations are more likely to
support one than the other, and hence the only thing that makes sense
to take both off the drawing board given the implication that neither
will garner implementation support (i.e., if one is "at risk", then
both must be).

Received on Tuesday, 19 April 2016 03:02:55 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 19 April 2016 03:02:56 UTC