W3C home > Mailing lists > Public > whatwg@whatwg.org > July 2009

[whatwg] ambiguity in <header> definition

From: Bruce Lawson <brucel@opera.com>
Date: Wed, 01 Jul 2009 15:08:40 +0100
Message-ID: <op.uwd6wqthh8on37@bruce-pc>
On Mon, 29 Jun 2009 14:54:48 +0100, Thomas Broyer <t.broyer at gmail.com>  
wrote:
  perhaps
>> the language should be tightened? ie ""A header element typically  
>> contains
>> the section's heading (an h1?h6 element or an hgroup element), but this  
>> is
>> not mandatory and may contain content such as navigation, a search form  
>> blah
>> blah"
>
> The fact that it is phrased as "typically contains ... but can also
> contain" makes it clear (for me) that it might contain a section's
> heading but this is not enforced (otherwise, it wouldn't say
> "typically")

my beef is with the words "can also contain", which suggest that it can  
contain other stuff in addition to h1..h6, hgroup (which it can) but it's  
ambiguous as to whether it must contain  h1..h6, hgroup as a minimum.  
(We're getting asked this a lot in html5doctor)



-- 
Hang loose and stay groovy,

Bruce Lawson
Web Evangelist
www.opera.com (work)
www.brucelawson.co.uk (personal)
Received on Wednesday, 1 July 2009 07:08:40 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 16:59:13 UTC