306525 2026-01-29 06:07:10 -0800 Keyboard Lock API Not Working STP 235 2026-03-24 18:27:49 -0700 1 1 1 Unclassified WebKit DOM Safari Technology Preview Mac (Apple Silicon) macOS 26 RESOLVED FIXED InRadar P2 Normal --- 1 possum.bracing0v sun.shin possum.bracing0v sun.shin webkit-bug-importer oldest_to_newest 2176173 0 possum.bracing0v 2026-01-29 06:07:10 -0800 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/ 2176361 1 webkit-bug-importer 2026-01-29 15:26:49 -0800 <rdar://problem/169219602> 2186790 2 sun.shin 2026-03-03 15:45:09 -0800 @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. 2186822 3 possum.bracing0v 2026-03-03 17:05:25 -0800 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. 2186901 4 sun.shin 2026-03-03 21:21:19 -0800 @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.