RESOLVED FIXED306525
Keyboard Lock API Not Working STP 235 
https://bugs.webkit.org/show_bug.cgi?id=306525
Summary Keyboard Lock API Not Working STP 235
Jeffrey Blanz
Reported 2026-01-29 06:07:10 PST
Keyboard Lock API does not work when using a Chrome Demo. Use the Link below and follow the steps under "Good Experience". https://googlechrome.github.io/samples/fullscreen-keyboard-lock/
Attachments
Add attachment proposed patch, testcase, etc.
Radar WebKit Bug Importer
Comment 1 2026-01-29 15:26:49 PST
<rdar://problem/169219602>
Byungseon(Sun) Shin
Comment 2 2026-03-03 15:45:09 PST
@Jeffery This is not a bug but as intended. The test page you shared is based on WICG Keyboard Lock API. And it is currently supported by Chrome browser (& Edge). https://webstatus.dev/features/keyboard-lock. And the way WebKit has is based on the Fullscreen based Keyboard Lock. Please refer to the discussion: https://github.com/whatwg/fullscreen/pull/232.
Jeffrey Blanz
Comment 3 2026-03-03 17:05:25 PST
I guess that’s probably why GeForce Now, Amazon Luna, and XCloud do not support it yet. Very essential for cloud gaming on macOS, visionOS, and iPads.
Byungseon(Sun) Shin
Comment 4 2026-03-03 21:21:19 PST
@Jeffrey, the content provider will decide which API implementations the service can utilize. It’s not always necessary to follow any specific APIs at this stage. As of now, there are no W3C standards in place to guide us.
Note You need to log in before you can comment on or make changes to this bug.