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

[Bug 11737] Change content model of <hgroup> to single <hx> + zero or more <sh> (sub/suphead) elements

From: <bugzilla@jessica.w3.org>
Date: Tue, 15 Feb 2011 07:02:21 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1PpEvV-0000BK-EV@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=11737

--- Comment #3 from Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no> 2011-02-15 07:02:19 UTC ---
(In reply to comment #2)
> (In reply to comment #1)

>In a HTML5 UA, <hgroup> has the "heading value" of the child with the highest
>heading value.
>Wheras in a HTML4 UA, <hgroup> would have no "heading value" whereas each hn
>child would have a heading value.

Please read teh above like so:

In a HTML5-UA, <hgroup> has the "outline value" of the child with the highest
heading value, and the same "heading value", except that it would be sudivied
in different internal levels.
Wheras in a HTML4 UA, <hgroup> would have no "heading value" whereas each hn
child would have a heading value. 

FURTHER more: if hgroup can contain a single hn plus one or more sh, then
legacy UAs and HTML5 UAs will - largely - agree about the outline result
(provided that HTML5's <section> and <article> are not used). They will also
_largelly_ agree about the headings they see. WIth the difference that the
HTML5-UA would see the sh elements as subheadings to the highest level heading
of headergroup element, while legacy-UAs will only see them as close to the
header and thus - at least if they come after the hn element, see them as
linked to that header, without themselves being headers in any way.

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Tuesday, 15 February 2011 07:02:23 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 15 February 2011 07:02:30 GMT