Bug 1987671 Comment 9 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

Original comment by
on 
FF148 MDN work for this can be tracked in https://github.com/mdn/content/issues/42752

To confirm, 
- prior to this change, all events other than `mousemove` and `pointermove` set `movementX` and `movementY` properties to zero. After this change, `pointerrawevent` can also have non-zero values.
- The values for `pointermove` potentially reflect the coalesced values of a number of events (i.e. `pointerrawevent`  events) while each `pointerrawevent` will be relative to the last `pointerrawevent` as per https://bugzilla.mozilla.org/show_bug.cgi?id=1987671#c7
- The pointer values are relative to the actual changes of the pointer even if the pointer is locked.
- The docs should be updated to make it clear that  `movementX` and `movementY` can also be set for  `pointermove` and  `pointerrawevent`.
- BCD 
  - should be updated to make it clear that FF148 is when Firefox started supporting non-zero values for those properties on  `pointerrawevent`
  - Can I assume `pointermove` has  supported values on those properties on FF for the same versions as `mousemove`?
  - Can I assume  chrome supported values on those properties for  `pointerrawevent` from its first version?
Revision 1 by
on 
FF148 MDN work for this can be tracked in https://github.com/mdn/content/issues/42752

Can you sanity check https://github.com/mdn/content/pull/42929 and 

- BCD 
  - should be updated to make it clear that FF148 is when Firefox started supporting non-zero values for those properties on  `pointerrawevent`
  - Can I assume `pointermove` has  supported values on those properties on FF for the same versions as `mousemove`?
  - Can I assume  chrome supported values on those properties for  `pointerrawevent` from its first version?

Back to Bug 1987671 Comment 9