[w3c/pointerlock] MovementX/Y values in coalesced events (#74)

The PointerLock [extension](https://w3c.github.io/pointerlock/#extensions-to-the-mouseevent-interface) defining `movementX/Y` also applies to `PointerEvent`s (as a subclass of `MouseEvent`), and that calls for a clarification in `movementX/Y` values "around" [coalesced events](https://w3c.github.io/pointerevents/#coalesced-events).

When Chrome decides not to send all `pointermove` events for performance reasons, the dispatched event's `movementX` (`movementY`) is updated to be the sum of individual `movementX` values (respectively `movementY` values) in coalesced events.

Should we add a line in the PointerLock spec mentioning it?

In PointerEvents spec, we had a non-normative text mentioning this idea but PEWG today [decided](https://github.com/w3c/pointerevents/pull/397) that it does not belong there.  In my opinion, the PointerLock spec should mention it because it would be useful for developers who care about `movementX/Y` values in individual coalesced events.

-- 
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/74