On Wed, 9 Jul 2014, Jonas Sicking wrote: > > > > This has been suggested many times, but the reason it's not part of > > the standard is that it's user-hostile. > > This argument always comes up, but I don't think this is an entirely > accurate statement. > > This is less user-hostile than the web platform is today. The web > platform today enables cancelling the contextmenu attribute which > disables the UA context menu.
That's why teh spec says: "User agents may provide means for bypassing the context menu processing model, ensuring that the user can always access the UA's default context menus. For example, the user agent could handle right-clicks that have the Shift key depressed in such a way that it does not fire the contextmenu event and instead always shows the default context menu." > Many website use this feature to replace the UA context menu with their > own context menu implemented in HTML. The result is a context menu which > is less accessible. It also results in that if the user uses UA features > to *not* make the UA context menu cancellable, then the UA context > overlays and hides the page provided one, making it inaccessible. Right, that's why contextmenu="" exists in the first place. All I'm saying is that we should strive for the ideal middle ground, where the page's context menu is given a strong presence, thus satisfying the author, but where the UA actions are still easily available. -- Ian Hickson U+1047E )\._.,--....,'``. fL http://ln.hixie.ch/ U+263A /, _.. \ _\ ;`._ ,. Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.' _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
