- From: Hamish Willee <notifications@github.com>
- Date: Thu, 23 Apr 2026 22:46:42 -0700
- To: whatwg/fullscreen <fullscreen@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
- Message-ID: <whatwg/fullscreen/pull/232/c4310976696@github.com>
hamishwillee left a comment (whatwg/fullscreen#232) Thanks so much @zcorpan et al for your help advice. Hope you can converge this soon. 1. > In addition, it is not entirely clear which keys should be intercepted and which should not. In FF151, I checked that Ctrl+W and Alt+Tab are not intercepted, although Chromium does it. It's a bit off-top, but nevertheless I would like to mention it: https://bugzilla.mozilla.org/show_bug.cgi?id=2034292 IMO - FWIW the uncertaintly is also a pain for users - it would be great to be a bit more precise about the interfaces we know can't be intercepted, such as Ctrl+Alt+Delete on Windows. 2. It would be convenient _for me_ to mandate exit via Esc long-press - it simplifies the docs and makes it easier to switch between browsers without having to learn something new. 3. When fullscreen first became a thing I didn't know you could exit it with ESC (I missed the notification - and there were a couple of weeks I was stuck in my browser banging kesy). This lock might have the same problem, at least in the short term. Worth thinking about multi-tap of esc popping up the notification again? -- Reply to this email directly or view it on GitHub: https://github.com/whatwg/fullscreen/pull/232?email_source=notifications&email_token=ACLYVMLUF46JJHRI4UOU76T4XL5UFA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTIMZRGA4TONRWHE3KM4TFMFZW63VKON2WE43DOJUWEZLEUVSXMZLOOS2XA4S7MNXW23LFNZ2F633QMVXF6Y3MNFRWW#issuecomment-4310976696 You are receiving this because you are subscribed to this thread. Message ID: <whatwg/fullscreen/pull/232/c4310976696@github.com>
Received on Friday, 24 April 2026 05:46:46 UTC