Issue metadata
Sign in to add a comment
|
Keyboard lock API launch tracker |
||||||||||||||||||||||||||||||
Issue descriptionChange description: Provide a mechanism by which full-screen apps can request keys such as Escape and combinations such as Alt+Tab that would normally be reserved by the browser or the OS. This is important for providing an immersive experience for apps such as games or remote desktop. Changes to API surface: navigator.requestKeyboardLock() and navigator.cancelKeyboardLock() See the W3C spec for details. Links: Public standards discussion: https://w3c.github.io/keyboard-lock/ Support in other browsers: None yet.
,
Sep 1 2017
This has not yet launched. I don't think it's related to your problem.
,
Sep 10 2017
Friendly reminder that this launch will require a type=launch issue for approvals tracking! Please link to it from here once it's created :)
,
Sep 12 2017
This issue has been automatically relabelled type=task because type=launch-owp issues are now officially deprecated. The deprecation is because they were creating confusion about how to get launch approvals, which should be instead done via type=launch issues. We recommend this issue be used for implementation tracking (for public visibility), but if you already have an issue for that, you may mark this as duplicate. For more details see here: https://docs.google.com/document/d/1JA6RohjtZQc26bTrGoIE_bSXGXUDQz8vc6G0n_sZJ2o/edit For any questions, please contact owencm, sshruthi, larforge
,
Jan 12 2018
We have a few tracking bugs for KeyboardLock so I am going to reduce it to a launch bug and an impl bug. Launch bug: crbug.com/677559 Impl bug: crbug.com/680809 |
|||||||||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||||||||
Comment 1 Deleted