W3C home > Mailing lists > Public > public-html@w3.org > September 2012

Re: Extension spec for hgroup (Was: Re: Getting HTML5 to Recommendation in 2014)

From: Sam Ruby <rubys@intertwingly.net>
Date: Tue, 25 Sep 2012 07:37:26 -0400
Message-ID: <50619776.1070509@intertwingly.net>
To: Henri Sivonen <hsivonen@iki.fi>
CC: Steve Faulkner <faulkner.steve@gmail.com>, "public-html@w3.org" <public-html@w3.org>, "w3c-wai-pf@w3.org" <w3c-wai-pf@w3.org>, "public-html-a11y@w3.org" <public-html-a11y@w3.org>, Jirka Kosek <jirka@kosek.cz>
On 09/25/2012 05:09 AM, Henri Sivonen wrote:
> On Mon, Sep 24, 2012 at 7:58 PM, Steve Faulkner
> <faulkner.steve@gmail.com> wrote:
>> I updated, http://www.html5accessibility.com/HTML5extensions/HTML5.html#interfaces
>> as requested.
> This proposal removes traces of the hgroup element from the parsing
> algorithm. Even if the working group decided to remove or split into
> module the hgroup element, it would be entirely inappropriate to
> remove it from the parsing algorithm. Browsers have shipped with
> hgroup-sensitive parsers and the parsing algorithm is sensitive to
> potentially non-conforming elements that have existed at some point in
> HTML's history—e.g. plaintext and xmp.

What specifically would you propose adding back in to address this?

As Jirka correctly indicates, if we were to start from a clean slate, 
clean and complete retention or removal might seem like better 
solutions; but we aren't starting from a clean slate here.

If retaining more of the parsing gets us to Recommendation faster, then 
that may be a win.

- Sam Ruby

[1] http://lists.w3.org/Archives/Public/public-html/2012Sep/0392.html
Received on Tuesday, 25 September 2012 11:40:36 UTC

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