Contact emails
Spec
https://github.com/w3c/pointerlock/pull/49
Summary
This is a change to the shipped PointerLock API. We are adding an options parameter which allows applications to request “unadjustedMouseMovement.” If the platform has this capability the element with pointer lock will receive raw mouse movement data as opposed to the standard accelerated mouse movements that Operating Systems normally provide. This is particularly useful for in-browser first person 3D navigation. This is in response to increasing requests from applications.
Intent To Prototype: https://groups.google.com/a/chromium.org/g/blink-dev/c/qZ_STHiTDzU/m/agsdSkVpDgAJ
Goals for experimentation
Validate that this option truly does resolve the mouse input issues that applications using Pointer Lock today are having.
Experimental timeline
Experiment begins in Chrome 81 and expires in Chrome 84
Any risks when the experiment finishes?
No, they will simply return to getting mouse movement data that is currently being provided by mouse events.
Ongoing technical constraints
None.
Will this feature be supported on all five Blink platforms supported by Origin Trials (Windows, Mac, Linux, Chrome OS, and Android)?
This release will only be on Windows. Windows is the only platform which provides a specific API for unadjusted mouse input to applications. Also, most users who have a mouse are on Windows. There are ongoing investigations on how to implement this on other platforms. The data provided from this API could help in convincing platforms that providing this option to applications would be worth the effort.
Feature Dashboard: https://www.chromestatus.com/feature/5723553087356928
--
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+...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/7fa4cebd-d8fd-46a2-912e-00df4e0a4cbb%40chromium.org.