Re: [w3c/pointerlock] Status report and planning for TPAC 2021 (#75)

### Spec changes since TPAC 2020
*   One normative change: [PR#68](https://github.com/w3c/pointerlock/pull/68) switched `movementX/Y` coordinates from integer type (`long`) to floating-point (`double`), to match CSSOM View Module [MouseEvent extension](https://drafts.csswg.org/cssom-view/#extensions-to-the-mouseevent-interface).
    *   This was the first step towards a bigger goal: allow precise movement tracking with fractional `screenX/Y` on high resolution screens (more precisely, screens with high [device pixel ratio](https://developer.playcanvas.com/en/user-manual/optimization/runtime-devicepixelratio)).
    *   Next stop: exposing floating-point `movementX/Y` values only in PointerEvents.  Also related [Issue #42](https://github.com/w3c/pointerlock/issues/42).
*   Quite a few editorial cleanups, thanks to [@marcoscaceres](https://github.com/marcoscaceres).

### Outstanding changes
*   [Issue #67](https://github.com/w3c/pointerlock/issues/67): remove redundant user activation definition because HTML already defines it.
    *   Work in progress, planning [this](https://github.com/w3c/pointerlock/pull/70#issuecomment-912772669) cleanup after landing a blocking [HTML change](https://github.com/whatwg/html/pull/7248).
*   [Issue #36](https://github.com/w3c/pointerlock/issues/36): supporting unaccelerated movement for a better gaming experience.
    *   [PR#49](https://github.com/w3c/pointerlock/pull/49) needs commitments from other browsers!
    *   Chrome is done with implementation behind a flag, and also with origins trials with Stadia and Nvidia's Geforce Now.  Currently blocked by the spec change above. Bug: [982379](https://bugs.chromium.org/p/chromium/issues/detail?id=982379).
    *   [Firefox asked](https://github.com/w3c/pointerlock/issues/36#issuecomment-526542010) about handling OS-specific challenges around system-wide settings, and [Chrome found solutions](https://github.com/w3c/pointerlock/issues/36#issuecomment-951444364) for almost all cases.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/pointerlock/issues/75#issuecomment-952230873