markbrown4 — 2010-01-19T17:13:56-05:00 — #1
Why haven't I seen the <menu> element before?
Why does everyone recommend people markup the menu's in <ul>'s if there's a <menu> tag for that?
Because it can't contain block level elements validly?
markbrown4 — 2010-01-19T17:16:24-05:00 — #2
I found it was deprecated on another page in the reference..
Then re-instated in HTML5 - standards are funny old things.
cupidstoejam — 2010-01-19T17:23:45-05:00 — #3
cooper_semantics — 2010-01-20T01:17:38-05:00 — #4
<menu> Is To Be Used For A List Of Commands And Is An Interactive Element And More Likely To Be Used Exclusively In Web Applications.
stevie_d — 2010-01-20T08:13:04-05:00 — #5
The <menu> tag was deprecated, as it wasn't felt to be particularly useful. It does not work consistently across different browsers, and it is not advisable to use it - <ul> does the job perfectly OK.
In HTML5, there will be a new <nav> element that adds the semantics of a navigation menu to the structure of a list.
cupidstoejam — 2010-01-20T12:24:33-05:00 — #6
Stevie, then why is the menu tag in the html5 spec? check my links above?
markbrown4 — 2010-01-20T16:20:55-05:00 — #7
Ok, so in HTML5 <nav> for navigation, <menu> for things like a toolbar. Sounds pretty straight-forward to me.