Currently, `movementX` and `movementY`
are supported only when `mousemove` or `pointermove`
as defined by the spec. However, Chrome supports this and this is
reported as a web-compat issue in the wild. I already filed the
spec issue to change the spec. So, we think the Chrome's behavior
is reasonable. Therefore, we'll follow them.
Bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1987671
Standard: https://w3c.github.io/pointerlock/#extensions-to-the-mouseevent-interface
Spec issues: https://github.com/w3c/pointerlock/issues/100 and https://github.com/w3c/pointerevents/issues/535
Platform coverage: All
Preference: dom.event.pointer.rawupdate.movement.enabled
DevTools bug: N/A
Other browsers: Chrome has already support it with `pointerrawupdate`,
I'm not sure about Safari.
web-platform-tests: No (The new behavior is tested with existing mochitests for now)
-- Masayuki Nakano <masa...@d-toybox.com> Working on DOM, Events, editor and IME handling for Gecko