Re: [w3c/pointerlock] TPAC 2022 status report (Issue #80)

### Spec changes since TPAC 2021
- One normative change:
  - [PR #76](https://github.com/w3c/pointerlock/pull/76) gets rid of “engagement gestures” in this spec in favor of “User Activation” in the HTML spec ([Sec 6.4 Tracking user activation](https://html.spec.whatwg.org/multipage/interaction.html#tracking-user-activation)).  The “engagement gestures” details were both incomplete and redundant after the HTML spec was updated a few years ago.  The two spec are now fully in-sync: all the details now belong to HTML, with `requestPointerLock` simply marked as a "transient activation-gated API".
- Lots of editorial cleanups, thanks to Marcos Cáceres ([@marcoscaceres](https://github.com/marcoscaceres)), Dominique Hazael-Massieux ([@dontcallmedom](https://github.com/dontcallmedom)) and Xiaoqian Wu ([@siusin](https://github.com/siusin)).

### Outstanding issues
- [Issue #25](https://github.com/w3c/pointerlock/issues/25) about Working Draft
  - [W3C Working Draft](https://www.w3.org/TR/pointerlock/) and [W3C Editor's Draft](https://w3c.github.io/pointerlock/) both point to 08 July 2022 version.
  - Perhaps an easy question for spec experts: do we still need the distinction?  Is the issue still relevant?
- [Issue #74](https://github.com/w3c/pointerlock/issues/74) MovementX/Y values in “coalesced events”
  - Spec overlap with PointerEvents, and PEWG decided that it does not belong there!
- [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) _still_ needs other browsers’ commitments!
  - We need to get out of this [unfortunate situation](https://github.com/w3c/pointerlock/pull/49#issuecomment-1041005606): Chrome [shipped](https://groups.google.com/a/chromium.org/g/blink-dev/c/cQn7OwcMQ64/m/uDi7C5oiAgAJ) to support Stadia and Nvidia's Geforce Now while facing lack of response.
  - [Mozilla raised](https://github.com/w3c/pointerlock/issues/36#issuecomment-526542010) the concern about OS-specific challenges around system-wide settings.  Does [our response ](https://github.com/w3c/pointerlock/issues/36#issuecomment-951444364)look good for that (modulo the Linux case)?
  - Chrome bug: [982379](https://bugs.chromium.org/p/chromium/issues/detail?id=982379).

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3c/pointerlock/issues/80#issuecomment-1243982683

You are receiving this because you are subscribed to this thread.

Message ID: <w3c/pointerlock/issues/80/1243982683@github.com>