Thanks for the heads up on this. Is the functionality complete in 130 already? I.e. is Chrome dev channel suitable for developers to test this behavior and confirm it works OK for their product? Or are there flags that should be turned on for testing still?
I assume this behavior is controlled via finch so that we have a kill-switch if needed (eg. if we get a report of a high-priority issue only once it rolls out to stable)? Thanks, Rick On Tue, Sep 10, 2024 at 3:26 AM 'Thomas Steiner' via blink-dev < blink-dev@chromium.org> wrote: > Created http://cl/672833499 (sorry, this is Google-internal) to document > this change. > > On Tue, Sep 10, 2024 at 1:01 AM 'Muyao Xu' via blink-dev < > blink-dev@chromium.org> wrote: > >> Contact emails >> >> muya...@google.com >> >> Specification >> >> Keyboard Lock API: https://wicg.github.io/keyboard-lock/ >> >> Pointer Lock API: https://www.w3.org/TR/pointerlock-2/ >> >> Chrome Status Entry >> >> https://chromestatus.com/feature/5142031990259712 >> >> Summary >> >> Show a permission prompt to the user when Keyboard Lock and/or Pointer >> Lock is requested by a website, and saves the user preferences as content >> settings. Currently, Keyboard.lock() and Element.requestPointerLock() both >> return a promise. The returned promise will be resolved if the permission >> is granted and the promise will be rejected if the permission is denied. >> >> The permission prompt notifies the user that the website is requesting >> Keyboard Lock and/or Pointer Lock, and allows them to explicitly choose >> whether to grant or deny those capabilities. This makes it more difficult >> for malicious websites (e.g., tech support scam websites) to gain the >> capabilities and prevent the user from exiting the website. >> >> Blink components >> >> Blink>Input >> <https://bugs.chromium.org/p/chromium/issues/list?q=component:Blink%3EInput> >> >> Tracking Bug >> >> crbug.com/314694812 >> >> Estimated milestone >> >> M130 >> >> -- >> You received this message because you are subscribed to the Google Groups >> "blink-dev" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to blink-dev+unsubscr...@chromium.org. >> To view this discussion on the web visit >> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAJRhUsYNE3X0h6bGqHYPo_eSjRSC50M9sqDTvfWie7-dzpNMJg%40mail.gmail.com >> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAJRhUsYNE3X0h6bGqHYPo_eSjRSC50M9sqDTvfWie7-dzpNMJg%40mail.gmail.com?utm_medium=email&utm_source=footer> >> . >> > > > -- > Thomas Steiner, PhD—Developer Relations Engineer (blog.tomayac.com, > toot.cafe/@tomayac) > > Google Germany GmbH, ABC-Str. 19, 20354 Hamburg, Germany > Geschäftsführer: Paul Manicle, Liana Sebastian > Registergericht und -nummer: Hamburg, HRB 86891 > > ----- BEGIN PGP SIGNATURE ----- > Version: GnuPG v2.4.3 (GNU/Linux) > > iFy0uwAntT0bE3xtRa5AfeCheCkthAtTh3reSabiGbl0ck > 0fjumBl3DCharaCTersAttH3b0ttom.xKcd.cOm/1181. > ----- END PGP SIGNATURE ----- > > -- > You received this message because you are subscribed to the Google Groups > "blink-dev" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to blink-dev+unsubscr...@chromium.org. > To view this discussion on the web visit > https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CALgRrLmoXtrUG2Sb1QZhNu3Zkp1A3WgFeDQ2fMFS_yUodWeNCQ%40mail.gmail.com > <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CALgRrLmoXtrUG2Sb1QZhNu3Zkp1A3WgFeDQ2fMFS_yUodWeNCQ%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > -- You received this message because you are subscribed to the Google Groups "blink-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+unsubscr...@chromium.org. To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAFUtAY_4ujcVEoeLORhopL9fjFBf%3D259gj5tgDw0r4hSGcmNTA%40mail.gmail.com.
