Suppressing the contextmenu is extremely user-hostile (for some users). There is a reason I always run with dom.event.contextmenu.enabled set to false.
If anything alters the existing context menu, make sure there is a pref to disable it. Even the disclosure chevron would be annoying to me. On 2014-06-29 00:30, Ian Hickson wrote: > On Sat, 28 Jun 2014, Dale Harvey wrote: >> >> Application developers have the ability to specify additional menuitems for >> contextmenus via >> http://www.whatwg.org/specs/web-apps/current-work/multipage/interactive-elements.html#context-menus >> however they are currently shown in addition to the default items, we are >> looking to implement an optional attribute that allows authors to disable >> the default context menu items so only the applications items are shown. >> This is primarily targeted for Firefox OS, I believe Jonas will be looking >> to add it to the official spec. >> >> The name / value of the attribute is under discussion >> >> <menu chrome="disabled"> >> <menuitem label="foo"></menuitem> >> </menu> >> >> looks like the most likely candidate. > > This has been suggested many times, but the reason it's not part of the > standard is that it's user-hostile. > > I would recommend that instead of letting the author prevent the user from > getting to the user's browser's commands, the browser instead simply hide > the browser commands behind a disclosure chevron, as in this example: > > > http://www.whatwg.org/specs/web-apps/current-work/multipage/interactive-elements.html#dom-contextmenu > _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
