[WSG] nav or menu?
Hi LG, I am making a site (html5) which has a nav section at the top of each page. Some pages will also have a 'menu' which will be a short list of links to other pages in the site, and these will appear lower down in the content of the page. Instinct tells me that it is sensible to make this subset as follows: menu dl ddblah/dd ddblah/dd ddblah/dd /dl /menu (where blah is a link to a page) But lots of folk seem to say that menu is only to be used for lists of commands. It's not clear to me, anyway! Is the above 'wrong'? All advice gratefully recd. Bob *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: memberh...@webstandardsgroup.org ***
Re: [WSG] nav or menu?
On 1/9/11 7:44 AM, designer wrote: Hi LG, I am making a site (html5) which has a nav section at the top of each page. Some pages will also have a 'menu' which will be a short list of links to other pages in the site, and these will appear lower down in the content of the page. Instinct tells me that it is sensible to make this subset as follows: menu dl ddblah/dd ddblah/dd ddblah/dd /dl /menu (where blah is a link to a page) But lots of folk seem to say that menu is only to be used for lists of commands. It's not clear to me, anyway! Is the above 'wrong'? All advice gratefully recd. Bob I do not think the above is necessarily wrong. Another approach might be: Top menu nav ul li/li ul /nav Subset menu nav ul id=s li/li ul /nav Best, ~d -- http://chelseacreekstudio.com/ http://chelseacreekstudio.com/fa/ *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: memberh...@webstandardsgroup.org ***
Re: [WSG] nav or menu?
This is a 'too early' post as HTML5 nav nor menu aren't really supported yet in any major browsers. So, we are speculating about how browsers might interpret these elements. You can read the HTML5 spec and see what is says about those tags, but at the end of the day browser implementation is going to dictate what is right or wrong. For now I would strongly suggest not putting either in your code, as you are simply adding bloat which serves no purpose whatsoever (until browsers start implementing these tags). Focus on the code which is going to deliver some value to your UI. Thanks, Jason On Sun, Jan 9, 2011 at 1:24 PM, David Laakso da...@chelseacreekstudio.comwrote: On 1/9/11 7:44 AM, designer wrote: Hi LG, I am making a site (html5) which has a nav section at the top of each page. Some pages will also have a 'menu' which will be a short list of links to other pages in the site, and these will appear lower down in the content of the page. Instinct tells me that it is sensible to make this subset as follows: menu dl ddblah/dd ddblah/dd ddblah/dd /dl /menu (where blah is a link to a page) But lots of folk seem to say that menu is only to be used for lists of commands. It's not clear to me, anyway! Is the above 'wrong'? All advice gratefully recd. Bob I do not think the above is necessarily wrong. Another approach might be: Top menu nav ul li/li ul /nav Subset menu nav ul id=s li/li ul /nav Best, ~d -- http://chelseacreekstudio.com/ http://chelseacreekstudio.com/fa/ *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: memberh...@webstandardsgroup.org *** -- Jason Grant BSc, MSc CEO, Flexewebs Ltd. www.flexewebs.com ja...@flexewebs.com +44 (0)7748 591 770 Company no.: 5587469 www.flexewebs.com/semantix www.twitter.com/flexewebs www.linkedin.com/in/flexewebs *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: memberh...@webstandardsgroup.org ***
Re: [WSG] nav or menu?
On 09/01/2011 13:32, Jason Grant wrote: This is a 'too early' post as HTML5 nav nor menu aren't really supported yet in any major browsers. So, we are speculating about how browsers might interpret these elements. You can read the HTML5 spec and see what is says about those tags, but at the end of the day browser implementation is going to dictate what is right or wrong. For now I would strongly suggest not putting either in your code, as you are simply adding bloat which serves no purpose whatsoever (until browsers start implementing these tags). Focus on the code which is going to deliver some value to your UI. nav doesn't have any new functionality of behaviour...it's simply a new structural element to denote navigation in a machine-readable way (like header, footer, aside, etc). It's a slightly more specific alternative to the generic div. Even once all browsers natively support it (giving it default block-level styling, amongst other things), they won't do anything different with it afaik. It's safe to use (with the usual caveat of IE support for unknown elements like this having to be plugged in via html5shim and default display:block styling having to be explicitly given). menu on the other hand is a planned interactive element. it is indeed meant for context menus, toolbars, etc, and once supported browsers will actually do something new and different with it. So long story short: between the two, I'd opt for nav. And (if you can live with the IE need for scripting) it's safe to use, though you won't get any benefit from it as such (other than more explicit semantics which *may* be of benefit to tools like screenreaders or search engine bots in future). But yes, failing all that, there's nothing wrong with a traditional div id=nav or whatever... P -- Patrick H. Lauke __ re·dux (adj.): brought back; returned. used postpositively [latin : re-, re- + dux, leader; see duke.] www.splintered.co.uk | www.photographia.co.uk http://redux.deviantart.com | http://flickr.com/photos/redux/ __ twitter: @patrick_h_lauke | skype: patrick_h_lauke __ *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: memberh...@webstandardsgroup.org ***
Re: [WSG] nav or menu?
The nav element is the correct element to use in the case of site navigation links. You are correct about menu which when implemented will be like a desktop app menu. The nav element is not generally accessibility supported in browsers yet, which means it's semantics are not conveyed, but you can add an ARIA landmark role to convey the meaning: nav role=navigation Regards Stevef Sent from my iPhone On 9 Jan 2011, at 12:44, designer desig...@gwelanmor-internet.co.uk wrote: Hi LG, I am making a site (html5) which has a nav section at the top of each page. Some pages will also have a 'menu' which will be a short list of links to other pages in the site, and these will appear lower down in the content of the page. Instinct tells me that it is sensible to make this subset as follows: menu dl ddblah/dd ddblah/dd ddblah/dd /dl /menu (where blah is a link to a page) But lots of folk seem to say that menu is only to be used for lists of commands. It's not clear to me, anyway! Is the above 'wrong'? All advice gratefully recd. Bob *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: memberh...@webstandardsgroup.org *** *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: memberh...@webstandardsgroup.org ***
