Could you please confirm that: 1. Keyboard Lock and Pointer Lock will continue to work in WebView scenarios 2. The new permissions prompt is compatible with full screen (which is a requirement for pointer lock)
If you have an example video or screenshots of the design for the new behavior, that would be super helpful. On Monday, September 9, 2024 at 4:01:09 PM UTC-7 Muyao Xu wrote: > Contact emails > > muy...@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/bbc15336-bd74-4052-9125-c7ff5fa0c02an%40chromium.org.
