[Bug 13608] Add <menuitem> element

http://www.w3.org/Bugs/Public/show_bug.cgi?id=13608

--- Comment #8 from Ian 'Hixie' Hickson <ian@hixie.ch> 2011-08-20 19:15:39 UTC ---
I don't understand the difference between a "command", a "menu item", and a
"toolbar button". Aren't they all just different ways of presenting the same
thing?

What's the graceful degradation behaviour of <menuitem>?

With the way the spec is written, you can write a menu or toolbar like this:

   <menu type="...">
    <a href="/">Home</a>
    <button onclick="save()">Save</button>
    <label>
      Shapes:
     <select onchange="insertShape(this.selectedOptions[0])">
      <optgroup>Insert
      <option>Rectangle
      <option>Circle
      <option>Triangle
     <select>
    </label>
   </menu>

...and in legacy UAs it would render as suggested by the markup above ignoring
the <menu>, and in a <menu>-aware UA if type="context" it would create a menu
that, when displayed, looks like this:

  ,---------.
  | Home    |
  | Save    ,-----------.
  | Insert >| Rectangle |
  `---------| Circle    |
            | Triangle  |
            `-----------'

...and if type="toolbar" it would create a toolbar that, when displayed, looks
like this:

   [Home] [Save] [Insert   v]
                 |Rectangle |
                 |Circle    |
                 |Triangle  |
                 '----------'

<command> is just a way to add commands to these menus in a way that does not
interfere with legacy UAs. It also, in the future, will allow us to add a way
to reference commands from other elements, e.g. maybe <a
command="home">Home</a> would create a link which, when clicked, would invoke
the <command id=home> command's onclick="" handler.

I just don't see why we'd have a <menuitem> element in this world.

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

Received on Saturday, 20 August 2011 19:15:42 UTC