- From: <bugzilla@jessica.w3.org>
- Date: Fri, 16 Dec 2011 17:23:55 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=13608
austin <tuseroni@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tuseroni@gmail.com
--- Comment #31 from austin <tuseroni@gmail.com> 2011-12-16 17:23:53 UTC ---
the arguments for <command> over <menuitem> are convincing. command seems to
have a lot to it, but when i think of <menu> i don't think of a nav bar, i
think of the context menu, we have a trillion ways to make a nav bar and NO way
to put things in the context menu.
a lot of the confusion seems like it would be settled by making either <menu> a
tag specifically for context menus or specifically for nav and a different tag
for context menus.
the things that someone might want for a nav bar (by this i mean your basic
drop down menu bar) are different from the things someone might want for
context menu (for instance i wouldn't want a 1024x768 image in my context menu,
or even a UL/li i have a general idea of what i expect a menu item to look like
in a context menu and i want the custom ones to look as much like that as
possible)
a nav bar on the other hand you expect a lot of markup, you expect it to be
styled and have drop downs with <input>s, <li>s,<img>s, etc
--
Configure bugmail: https://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 Friday, 16 December 2011 17:23:57 UTC