Open Bug 854401 Opened 13 years ago Updated 3 years ago

site should be able to request permission for oncontextmenu.event.preventDefault

Categories

(Core :: DOM: Events, enhancement, P5)

21 Branch
enhancement

Tracking

()

People

(Reporter: beta, Unassigned)

References

Details

(Whiteboard: [bugday-20131021][bugday-20131106])

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:21.0) Gecko/20130323 Firefox/21.0 Build ID: 20130323042013 Steps to reproduce: Visited http://codepen.io/stuffit/pen/KrAwx Right click is used on the canvas in the example, the context menu currently gets in the way. Google Maps, Youtube’s HTML5 video player and other sites have the same UX issue with Firefox’s context menu overlapping their custom menu. Until HTML5’s <section contextmenu=""> becomes popular, this will still be a problem for desktop users… On first calling event.preventDefault inside oncontextmenu, a doorhanger permission could ask the user for permission to allow this for the site.
OS: Linux → All
Hardware: x86_64 → All
Could you provide a screenshot of the issue, please.
Flags: needinfo?(john)
Firefox' Menu get's properly disabled over here (Win 7 x64). Do you have dom.event.contextmenu.enabled;false set?
(In reply to XtC4UaLL [:xtc4uall] from comment #2) > Firefox' Menu get's properly disabled over here (Win 7 x64). > Do you have dom.event.contextmenu.enabled;false set? I do, forgot to mention this is more of a feature request for the future when/if Bug 851702 removes the advanced js options. Sites cannot go fullscreen without permission, and I have the same expectation for browser chrome.
Flags: needinfo?(john)
This works fine with dom.event.contextmenu.enabled=TRUE on Aurora 21.0a2 (2013-04-01).
Blocks: useragent
Severity: normal → enhancement
Whiteboard: [bugday-20131021]
(In reply to Paul Silaghi, QA [:pauly] from comment #4) > This works fine with dom.event.contextmenu.enabled=TRUE on Aurora 21.0a2 > (2013-04-01). John means the user should be able to decide whether to allow the current site to disable the menu, e.g., for the session only.
Status: UNCONFIRMED → NEW
Ever confirmed: true
And if the user refuses, the site should not know the user called the local menu, so as not cause confusing events like two menus over each other or a video being (un)paused accidentally.
Component: Untriaged → DOM: Events
Product: Firefox → Core
See Also: → 379210
Whiteboard: [bugday-20131021] → [bugday-20131021][bugday-20131106]
Websites should use HTML5 context menus (though some issues need to be fixed before they are particularly useful, especially Bug 705292 and Bug 897102). This preempts the need for adding a Firefox-only API which nags the user unnecessarily.
https://bugzilla.mozilla.org/show_bug.cgi?id=1472046 Move all DOM bugs that haven’t been updated in more than 3 years and has no one currently assigned to P5. If you have questions, please contact :mdaly.
Priority: -- → P5
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.