Status report and planning for TPAC 2021

[LJWatson]

TPAC will be virtual again this year. There will be a WebApps WG meeting at some point between 24 and 29 October.

There are two things we need you to do in the meantime:

1. Let @marcoscaceres and I know before 17 September if you plan to hold a specification specific meeting (in addition to the general WebApps WG meeting)
2. Post a specification status report before 30 September

Your specification status report should include:

• What progress has your spec made in the last 12 months?
• Is anything blocking your spec from moving to CR?
• If yes, what is your plan to unblock it and do you need any help?

CC @siusin

[reillyeon]

I recommend discussing the status of https://github.com/w3c/pointerlock/pull/49. CC @nondebug.

[marcoscaceres]

Reminder that the WG is meeting on Tuesday 26 October 2021, 9PM to 11PM UTC.

It would great if someone could give an 5 minute update on the state of this spec.

[nondebug]

I can summarize the current state of the spec along with the status on PR #49

[mustaqahmed]

Thanks @nondebug for covering un-accelerated movementX/Y part. I will provide a quick update on the overall state plus last year's changes.

[marcoscaceres]

Thanks you both! See you tomorrow.

[mustaqahmed]

Spec changes since TPAC 2020

• One normative change: PR#68 switched movementX/Y coordinates from integer type (long) to floating-point (double), to match CSSOM View Module MouseEvent extension.
  • 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).
  • Next stop: exposing floating-point movementX/Y values only in PointerEvents. Also related Issue #42.
• Quite a few editorial cleanups, thanks to @marcoscaceres.

Outstanding changes

• Issue #67: remove redundant user activation definition because HTML already defines it.
  • Work in progress, planning this cleanup after landing a blocking HTML change.
• Issue #36: supporting unaccelerated movement for a better gaming experience.
  • PR#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.
  • Firefox asked about handling OS-specific challenges around system-wide settings, and Chrome found solutions for almost all cases.