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

mustaqahmed left a comment (w3c/pointerlock#104)

Thanks for filing this issue!

Before we look into this, I would suggest a simplified view of the problem here because PointerLock affects only _mouse_ pointers by definition, and that in practice no system exposes a non-primary mouse pointer (see the last "note" in [Section 4.1.2](https://w3c.github.io/pointerevents/#the-primary-pointer)). So I would suggest dropping the `pointerId` condition here and adding a line in the spec to emphasize that PointerLock is only about _primary_ mouse pointers. What do you think?

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

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