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

Re: 3.8.3. The nav element

From: Simon Pieters <simonp@opera.com>
Date: Sat, 19 Jan 2008 19:08:49 +0100
To: "Ben Boyle" <benjamins.boyle@gmail.com>, HTMLWG <public-html@w3.org>
Message-ID: <op.t46vczdfidj3kv@hp-a0a83fcd39d2.belkin>

On Sat, 19 Jan 2008 12:17:06 +0100, Ben Boyle <benjamins.boyle@gmail.com>  

> Hope you've enjoyed this quick look at the relationship between
> header, footer and nav. I'm keen to hear more opinions. Am I on track
> in thinking that nesting nav inside header/footer will be useful? Have
> I missed the point somewhere? Discuss.

I can see the value in having <nav> be a sectioning element with its own  
subsections. e.g. on w3.org home page I would say that the whole left  
sidebar is a <nav>. OTOH I have also seen pages that use navigation in  
headers and footers, so I would expect authors to be surprised when their  
<header><nav> or <footer><nav> markup doesn't validate when they make an  
effort to convert their <div> soup to HTML5. Hence, I agree that <nav>  
should be allowed to be nested in <header> and <footer> (but then have  
transparent content model).

Simon Pieters
Opera Software
Received on Saturday, 19 January 2008 18:09:05 UTC

This archive was generated by hypermail 2.4.0 : Saturday, 9 October 2021 18:44:25 UTC