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

masayuki-nakano created an issue (w3c/pointerlock#104)

It's defined as having non-zero values for `pointermove` and I suggested that they should be available with `pointerrawupdate` too.
* https://github.com/w3c/pointerlock/issues/100
* https://github.com/w3c/pointerevents/issues/535

However, the Pointer Lock 2.0 spec does not mention about `pointerId`. I think that the values should be difference from the corresponding event whose `pointerId` is the same as the event.

E.g., when there are 2 pointers,
1. `pointermove` for `pointerId: 1`
2. `pointermove` for `pointerId: 2` (should be zero)
3. `pointerrawupdate` for `pointerId: 1` (should be diff from the first `pointermove`)
4. `pointerrawupdate` for `pointerId: 1` (should be diff from the previous `pointerrawupdate`)
5. `pointermove` for `pointerId: 1` (should be diff from the first `pointermove`)
6. `pointerrawupdate` for `pointerId: 2` (should be diff from the second `pointermove`)
7. `pointerrawupdate` for `pointerId: 2` (should be diff from the previous `pointerawupdate`)
8. `pointermove` for `pointerId: 2` (should be diff from the second `pointermove`)

ccing: @smaug---- @mustaqahmed @daxpedda

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

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