- From: <bugzilla@jessica.w3.org>
- Date: Mon, 22 Aug 2011 20:16:40 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=12999 --- Comment #10 from Jonas Sicking <jonas@sicking.cc> 2011-08-22 20:16:39 UTC --- Tab: I don't quite understand what UI you are advocating for. What I'm saying is that pages currently use the contextmenu event + piles of <div>s in order to create their own context menu and remove the default one. The <menu> element provides an opportunity to create a better situation. By adding a @nodefault attribute, we allow websites to semantically describe that they want their context menu options to replace the default set of options. This gives UAs a lot more freedom in creating a good user experience than the current contextmenu event + piles of <div>. With a @nodefault attribute UAs can expose UI to temporarily or permanently ignore the @nodefault. For example UAs can have an option "allow sites to replace context menu" which chooses if @nodefault should be ignored or not. Or they can add a option at the bottom which exposes the default menu as a sub-menu. Or add an option which says "don't allow this website to replace my context menu". UAs could even choose to expose only a set of most critical options when @nodefault is set. Currently none of those things are possible. Could you describe what you are hoping or expecting will happen as long as we don't have @nodefault but still do have the context menu event? -- 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 Monday, 22 August 2011 20:16:42 UTC