Closed Bug 1314856 Opened 8 years ago Closed 8 years ago

Fullscreen websites are prevented from capturing browser shortcuts like Ctrl+W

Categories

(Core :: DOM: UI Events & Focus Handling, defect)

49 Branch
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 380637

People

(Reporter: mgiuca, Unassigned)

Details

User Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2906.0 Safari/537.36 Steps to reproduce: 1. Visit http://dominickng.com/chromium-demos/fizz/keyboard-combinations/combinations.html 2. Press Go Fullscreen. 3. Press Ctrl+W. Actual results: Exits fullscreen and closes the tab. Expected results: Site captures the key, printing "Ctrl-W" and not exiting fullscreen (due to call to preventDefault). Discussion: I'm not sure if this is a bug per se. It's possibly intentional to prevent sites from capturing browser shortcuts, but we noticed a change in Firefox's behaviour some time in the past year (we looked at it a year ago and found that you could capture these keys in fullscreen). We (Dominick and myself) are on the Google Chrome team. Chrome doesn't currently let sites capture these shortcuts but we are considering changing to that behaviour *in fullscreen only*. The philosophy is that when an app has fullscreen, you don't need ordinary browser shortcuts like tab management, and it should feel more like a full application. The only shortcut that must not be capturable by the site is Esc which is used to exit fullscreen. If this was a deliberate change, I was wondering if whoever did it could provide rationale for why it was changed. Also I believe Microsoft Edge does allow sites to capture these shortcuts (both in and out of fullscreen).
Component: Untriaged → Keyboard Navigation
Component: Keyboard Navigation → Event Handling
Product: Firefox → Core
Thanks. I'll mark as a dupe and follow up there.
Status: UNCONFIRMED → RESOLVED
Closed: 8 years ago
Resolution: --- → DUPLICATE
Component: Event Handling → User events and focus handling
You need to log in before you can comment on or make changes to this bug.