W3C home > Mailing lists > Public > public-html@w3.org > January 2011

Re: rationale for inclusion of hgroup in html5?

From: Simon Pieters <simonp@opera.com>
Date: Thu, 27 Jan 2011 21:30:28 +0100
To: "Jirka Kosek" <jirka@kosek.cz>, "James Graham" <jgraham@opera.com>
Cc: "Leif Halvard Silli" <xn--mlform-iua@xn--mlform-iua.no>, "Steve Faulkner" <faulkner.steve@gmail.com>, "Anne van Kesteren" <annevk@opera.com>, "HTML WG" <public-html@w3.org>
Message-ID: <op.vpzhw2x6idj3kv@simon-pieterss-macbook.local>
On Thu, 27 Jan 2011 17:11:54 +0100, James Graham <jgraham@opera.com> wrote:

> On 01/27/2011 04:15 PM, Jirka Kosek wrote:
>> - all<hx>  elements are considered
>> - if there are multiple<hx>  elements inside<header>  only first of them
>> is considered
> That was, in fact, the very first solution that we developed. However  
> people seemed to find it confusing (iirc they didn't want <header> to  
> have anything to do with the outline algorithm). <hgroup> was an attempt  
> to fix that. It seems that the design is still considered suboptimal,  
> hence ideas like <subhead> and so on.

One issue with the first <header> design was that people want to put <nav>  
and <aside> in <header>, which was not allowed since they're sections and  
it would be confusing if <header> would disable nested implicit sections  
but allow nested explicit sections, or something like that.

Simon Pieters
Opera Software
Received on Thursday, 27 January 2011 20:31:07 UTC

This archive was generated by hypermail 2.4.0 : Saturday, 9 October 2021 18:45:30 UTC