W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > August 2011

[Bug 12999] Allow nodefault="" on <menu type=context>

From: <bugzilla@jessica.w3.org>
Date: Tue, 23 Aug 2011 05:30:53 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1QvjZd-0004ZU-Lk@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=12999

Ian 'Hixie' Hickson <ian@hixie.ch> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|REOPENED                    |NEW

--- Comment #13 from Ian 'Hixie' Hickson <ian@hixie.ch> 2011-08-23 05:30:53 UTC ---
I think before we add this we should find out (by exposing the feature) whether
authors so object to the native menu that they won't accept to coexist with it
(and will instead continue to use <div>s) or if they in fact would be happy to
coexist with it but today are simply incapable of doing so.

Note that the spec doesn't require that the elements be merged inline. They
could be hidden behind a single context menu item. The merged items could be a
subset of the full menu. The UA menu could be entirely hidden unless the user
had brought up the menu while holding the shift key down. The UA could be
entirely hidden if the user brought up the menu with the right mouse button but
shown if the user used two fingers when pressing on the multitouch right mouse
button. Only in some of these scenarios does it even make sense to expose a
control to the author about what to do.

Unless and until we have a better understanding of what implementations
converge on and what authors actually want, it's impossible IMHO to make an
educated decision on how to support the proposal.

-- 
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 Tuesday, 23 August 2011 05:30:55 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 16:31:17 UTC