W3C home > Mailing lists > Public > public-html@w3.org > December 2010

Re: suggestion for abolition of <hgroup>

From: Karl Dubost <karld@opera.com>
Date: Wed, 1 Dec 2010 06:38:38 -0500
Message-Id: <7BD39A15-2156-458B-8B5F-27EB1FD6EFC0@opera.com>
Cc: "Leif Halvard Silli" <xn--mlform-iua@xn--mlform-iua.no>, "HTML WG" <public-html@w3.org>
To: Bruce Lawson <brucel@opera.com>

Le 30 nov. 2010 à 09:24, Bruce Lawson a écrit :
> <header>
> <h1>brucelawson.co.uk</h1>
> <h2>Gorgeousness in a gimp mask</h2>
> </header>
> 
> magically removes the h2 from the outline, as it's adjacent to the <h1>

magic (position) and behavior changes (hgroup) are both confusing for people who have not read the specification carefully. ok let see. Let's keep heading for heading, and that's all. Maybe the issue to fix is the algorithm for outlining. 

A common pattern is:

<header>
    <h1>brucelawson.co.uk<br/>
        <span class="subtitle">Gorgeousness in a gimp mask</span>
    </h1>
</header>

Which would extract the full sentence for the outline, and that can be fine.
Or maybe you wanted just the first part,

<header>
    <h1 title="brucelawson.co.uk">brucelawson.co.uk<br/>
        <span class="subtitle">Gorgeousness in a gimp mask</span>
    </h1>
</header>

And in this case the algorithm would take the content of the title attribute on the h1, or any other headings. If title is not convenient it could be a specific attribute.

Would that create an accessibility issue? 

-- 
Karl Dubost - http://dev.opera.com/
Developer Relations & Tools, Opera Software
Received on Wednesday, 1 December 2010 11:39:24 UTC

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