On Monday, December 8, 2025 at 3:50:34 PM UTC+1 Chromestatus wrote:

*Contact emails*
[email protected], [email protected]

*Specification*
https://www.w3.org/TR/pointerlock-2 

*Summary*
Provides access to raw mouse movement by locking the target of mouse events 
to a single element and hiding the mouse cursor. 

*Blink component*
Blink>Input>PointerLock 
<https://issues.chromium.org/issues?q=customfield1222907:%22Blink%3EInput%3EPointerLock%22>

*Web Feature ID*
pointer-lock <https://webstatus.dev/features/pointer-lock> 

*Motivation*
The Pointer Lock API provides applications the ability to directly 
interpret mouse movements as an input method, rather than being limited to 
only reading the position of the mouse cursor. A popular example is that of 
first person movement controls in three dimensional graphics applications 
such as games: movement of the mouse is interpreted to control the 
rotation/direction of the player's camera; no mouse cursor is displayed, 
and the movement is not limited to the traditional boundaries (such as the 
user agent's window, or the overall screen) that the mouse cursor is 
usually subject to, meaning that any mouse movements can be tracked 
indefinitely in any direction. See a Simple Demo: (
https://mdn.github.io/dom-examples/pointer-lock/), and used in e.g. Xbox 
Cloud Gaming, GeForce Now, Amazon Luna, poki.com, crazygames.com, 
autodesk.com, etc. The pointer lock API is supported on Desktop platforms, 
this feature is for supporting this API for Android. 

*Initial public proposal*
*No information provided*

*TAG review*
*No information provided*


Was the desktop API reviewed?
 



*TAG review status*
Not applicable 

*Risks*


*Interoperability and Compatibility*
*No information provided* 

*Gecko*: No signal

*WebKit*: No signal


Can you file for Gecko/WebKit signals? Did we get signals for the desktop 
feature?
 


*Web developers*: No signals


Presumably, someone wants to use this?
 


*Other signals*:

*WebView application risks*

Does this intent deprecate or change behavior of existing APIs, such that 
it has potentially high risk for Android WebView-based applications? 
*No information provided* 


*Debuggability*
*No information provided* 

*Will this feature be supported on all six Blink platforms (Windows, Mac, 
Linux, ChromeOS, Android, and Android WebView)?*
No

*Is this feature fully tested by web-platform-tests 
<https://chromium.googlesource.com/chromium/src/+/main/docs/testing/web_platform_tests.md>?*
No


Is the Desktop feature tested?
 




*Flag name on about://flags*
*No information provided* 

*Finch feature name*
PointerLockOnAndroid 

*Rollout plan*
Will ship enabled for all users

*Requires code in //chrome?*
False

*Tracking bug*
https://g-issues.chromium.org/issues/40290045

*Launch bug*
https://launch.corp.google.com/launch/4386186

*Estimated milestones*
Shipping on Android144 

*Anticipated spec changes*

Open questions about a feature may be a source of future web compat or 
interop issues. Please list open issues (e.g. links to known github issues 
in the project for the feature specification) whose resolution may 
introduce web compat/interop risk (e.g., changing to naming or structure of 
the API in a non-backward-compatible way). 
*No information provided*

*Link to entry on the Chrome Platform Status*
https://chromestatus.com/feature/6739764319485952?gate=4680627611893760

This intent message was generated by Chrome Platform Status 
<https://chromestatus.com>. 

-- 
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 [email protected].
To view this discussion visit 
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/c727a2d2-3fb6-405b-8322-db15a32a94f0n%40chromium.org.

Reply via email to