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

[whatwg] several messages

From: Ian Hickson <ian@hixie.ch>
Date: Thu, 31 Jul 2008 01:12:34 +0000 (UTC)
Message-ID: <Pine.LNX.4.62.0807310111050.3299@hixie.dreamhostps.com>
On Thu, 12 Jun 2008, Jorge Bay Gondra wrote:
>
> I was trying to imaging how it would be to build a site, and I realized 
> that, in the case of site with 2 nav bars (typically 2 sidebars) there's 
> not a way to specify which is the "main" sidebar and which is 
> accessory... What do you think about specifying hierarchy for navs 
> elements?

On Fri, 13 Jun 2008, James Graham wrote:
> 
> Arguably the outline algorithm already does this, since it places <nav> 
> elements in a hierarchy along with other sections. For any case not 
> covered by the outline algorithm I think that there would need to be 
> some very strong use cases to add explicit markup here; what kind of UA 
> features did you have in mind, and how well would they work if the 
> markup was missing or incorrect on most pages?

I agree with James here, what is the use case?


On Thu, 12 Jun 2008, Jorge Bay Gondra wrote:
>
> Note: In the nav sample ( 
> http://www.whatwg.org/specs/web-apps/current-work/multipage/the-root.html#the-nav) 
> that includes several places with links, should be a good idea that the 
> header and footer list of links have to be represented in an unordered 
> list ul..., and not in a paragraph (!?), do you agree?

Doesn't really matter either way. Do can do whatever you like. :-)

-- 
Ian Hickson               U+1047E                )\._.,--....,'``.    fL
http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'
Received on Wednesday, 30 July 2008 18:12:34 UTC

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