Re: [whatwg/fullscreen] Keyboard lock (Issue #231)

> Sites can of course not bother to listen for certain codes, as is their prerogative. But they would receive them all.

It's worth noting that even if a site ignores a certain key, the fact of intercepting it at the OS level changes its behaviour. The canonical example of this is a full-screen game that wants to:

* intercept the Windows key (because it's easy to hit by accident, and its default behaviour of opening the Start menu is annoying when playing the game); but
* leave Alt+Tab with its default action, because switching to a web browser to consult a walkthrough is useful.

We can't just intercept all keys and let the game ignore Alt+Tab, because then there's no way to "re-inject" it to support the second scenario. That's how we ended up with the current API design where the set of desired keys must be declared up-front.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/fullscreen/issues/231#issuecomment-1843505251
You are receiving this because you are subscribed to this thread.

Message ID: <whatwg/fullscreen/issues/231/1843505251@github.com>