- From: Philip Jägenstedt <notifications@github.com>
- Date: Thu, 07 May 2026 04:18:37 -0700
- To: whatwg/fullscreen <fullscreen@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Thursday, 7 May 2026 11:18:45 UTC
foolip left a comment (whatwg/fullscreen#232) > @foolip does Google have thoughts about usefulness of this API? One of my concerns is that, given browser shortcuts are already locked on fullscreen without keyboard lock on Safari and Chrome, people will not care about this API unless they care about Escape key behavior. > > Edit: And the same question also applies to Blink's navigator.keyboard.lock, to me the API looks much less useful now compared to when it was introduced, because of the same reasons above. I'm reviewing this as spec editor and am not planning to implement anything myself, so no implementer interest from Google. But that isn't needed process wise since Apple and Mozilla do want this change. That being said, given how "declarative" this API is I think it should be possible to define it in terms of the keyboard lock API later if we want to do that, or at the very least define how they interact. But to figure that out really requires an attempt to implement this, I think. -- Reply to this email directly or view it on GitHub: https://github.com/whatwg/fullscreen/pull/232#issuecomment-4396630384 You are receiving this because you are subscribed to this thread. Message ID: <whatwg/fullscreen/pull/232/c4396630384@github.com>
Received on Thursday, 7 May 2026 11:18:45 UTC