Jon, can you please link to the type=launch issue here and mark that as blocking this so we ensure that the relevant approvals (e.g. security) are completed before this launches?

If you're curious to learn more about how type=launch issues differ from type=launch-owp issues you can see this doc: https://drive.google.com/open?id=1Z9x-PBYgDaR99tsNLvhibZLeAwDR757Gor--I60ygeE

Thanks Owen, from reading the doc, it looks like we need one of both. Gary, can you open a new parallel bug to track the internal approvals?

Thanks Jon. Just nudging here, is there now a type=launch issue to mark as blocking this? Thanks!

Spec has been moved to the W3C github repo:
https://github.com/w3c/keyboard-lock

Link to W3C ED:
https://w3c.github.io/keyboard-lock/

Also note the name has been updated to simply "Keyboard Lock" since the feature is not restricted to System level keys.

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

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