Le 10 juil. 2014 à 14:57, Jonas Sicking <jo...@sicking.cc> a écrit : > 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.
A suggestion from the naive-poet-department: What about something where, the main contextual menu is become a child of the developer menu. Would it be an acceptable compromise? normal system: ┌ default-item 1 ├ default-item 2 └ default-item 3 When the developer creates a contextual menu ┌ dev item 1 ├ dev item 2 ├ dev item 3 └ default-sys ├ default-item 1 ├ default-item 1 └ default-item 3 so basically, it is still available but just not deployed except if the user is hovering on default-sys. -- Karl Dubost, Mozilla http://www.la-grange.net/karl/moz _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
