Unclear if `pointermove` should set `movementX/Y`

[daxpedda]

According to the spec:

pointerlock/index.html

Lines 629 to 630 in 0e99fcf

	{{movementX}} and {{movementY}} must be zero for all mouse events
	except `mousemove`. All motion data must be delivered via

Which seems to imply that movementX/Y should be zero for pointermove. Is this intentional?

See https://bugzilla.mozilla.org/show_bug.cgi?id=1753724, where this has come up.

[mustaqahmed]

Thanks for the catch, I believe this is unintentional because the text predates cross-browser support for PointerEvents.

FYI: in Chrome we set movementX/Y in pointermove events. If I recall correctly, when shipping PointerEvents we interpreted the spec text:

... all mouse events except mousemove

as

... all MouseEvents except mousemove

which leaves PointerEvents unspecified here. So we extended the mousemove behavior to pointermove.

[daxpedda]

Thanks!

Should I open a PR doing that exact change?
Or should it rather just say "except mousemove and pointermove"?

[mustaqahmed]

Or should it rather just say "except mousemove and pointermove"?

This sounds better.

[smaug----]

which leaves PointerEvents unspecified here

Well, the spec says that the properties are 0 by default, and nothing says they should be something else on pointermove, so ... ;)

[mustaqahmed]

I just approved #101 after confirming that both Chrome and Firefox already set pointermove.movementX/Y correctly outside the coalesced event lists.