2 ms·
Note that this proposal is still in Editors Draft (meaning it hasn't even been proposed as a Working Draft yet, they're still in the process of writing the init
by danShumway 8y ago
Note that this proposal is still in Editors Draft (meaning it hasn't even been proposed as a Working Draft yet, they're still in the process of writing the initial proposal). It could very well be rejected, and I hope it is.
It's being championed by the Chromium team, and just because Chromium has turned something on doesn't mean it's a standard. It just means that Chromium doesn't know how to properly launch experimental browser settings behind user flags, <rant>because apparently we've all learned literally nothing from the early days of browser-specific CSS tags and the botched release of flexbox</rant>.
Remember HTML imports, Observable, etc... there's still plenty of time to file issues[0] and participate in conversation about the feature[1]. And I encourage you to do so, because speaking as a game developer on the web, this is a bad feature that shouldn't be built.
[0]: https://github.com/w3c/keyboard-lock/issues https://github.com/w3c/keyboard-lock/issues
[1]: https://discourse.wicg.io/t/proposal-system-keyboard-lock-api/1594 https://discourse.wicg.io/t/proposal-system-keyboard-lock-ap...