Re: [w3c/pointerlock] `movementX` and `movementY` for `pointermove` (and `pointerrawupdate`) should be the difference from the previous event for the same `pointerId` (Issue #104)

kvnloo left a comment (w3c/pointerlock#104)

Chromium already carries coalesced events through `PointerEventManager` when constructing pointer events.

That makes the definition of "previous event" particularly important: previous dispatched event and previous underlying hardware/coalesced sample are observably different concepts.

For low-latency input consumers, defining deltas relative to the underlying ordered sample sequence would avoid movement depending on how aggressively the UA coalesces dispatch.


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

Message ID: <w3c/pointerlock/issues/104/5941895048@github.com>