[5.1] the menu element and its usage as application menubar

The definition of the 'menu' element allows to create toolbars and
popup menus in html5 but it does not allow standalone application
menubars.

 
http://www.w3.org/html/wg/drafts/html/master/interactive-elements.html#the-menu-element

To have a more concrete idea of what's missing, see this screenshot:

   http://quaxe.org/public/quaxe/quaxe-teaser2.png

This is a real example, built to native from html 5 (don't look
too much at the markup, look at the result please):

   http://quaxe.org/public/quaxe/quaxe-teaser2.png

The ARIA role attribute allows to specify role="menubar" but the type
attribute can only carry "toolbar" or "popup" and its default value when
ommitted is "toolbar". I think we really need a way of specifying an
application menubar and we need to define its content model better...

For example, the current model for <menu type="toolbar"> allows the
following:

   <menu type="toolbar">
     <li><span contextmenu="filemenupopup">File</span>
       <menu type="popup" id="filemenupopup">
         ...
       </menu>
       foooooo</li>
   </menu>

What's the fate of the "foooooo" text node here? And why do I need
a contextmenu attribute (as said in the spec) on a useless span
since I have a menu element inside my li element?

I think the model for this <menu> element is badly designed, and
painful to implement. I would recommend revamping it entirely;
the too lax <li> element does not seem to me the right choice here.

</Daniel>

Received on Wednesday, 19 November 2014 15:02:01 UTC