8000 Suggestion for the support of Keyboard Lock API · Issue #385 · w3c/uievents · GitHub

More Web Proxy on the site http://driver.im/

Suggestion for the support of Keyboard Lock API #385

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Open

xingri opened this issue Sep 27, 2024 · 2 comments

Assignees

Labels

TPAC2024

xingri commented

As of today, there are two different implementation ideas of Keyboard Lock API.

As the Chrome is adding user prompt for the user permission, is there a chance to unifying the implementation?

Chromium Proposal: https://github.com/WICG/keyboard-lock/
Mozilla and WebKit: Keyboard lock whatwg/fullscreen#231

xingri added the TPAC2024 label

xingri changed the title ~~Proposal to support Keyboard Lock API~~ Suggestion for the support of Keyboard Lock API

Author

xingri commented

Chromium issue: https://issues.chromium.org/issues/410607899
WebKit Issue: https://bugs.webkit.org/show_bug.cgi?id=264843

xingri self-assigned this

Author

xingri commented

@garykac I have started discussion on Chromium issue to get the chrome team's opinion on integrating the Keyboard Lock API into the Full Screen API.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

0