Oh, [the test expects that another synthesized `eMouseMove` should happen when `ePointerOut` is fired by a synthesized `eMouseMove`](https://searchfox.org/mozilla-central/rev/e24d8f4dd564d9fa0beed22224db1d153c22d95b/testing/web-platform/tests/pointerevents/pointerevent_pointerout_no_pointer_movement.html#48-49,52,58). [However, we do not allow that to prevent infinite reflow loop](https://searchfox.org/mozilla-central/rev/e24d8f4dd564d9fa0beed22224db1d153c22d95b/layout/base/PresShell.cpp#6004-6008). I think that this limitation is reasonable. That could cause infinite flickering and/or making a clickable element unavailable. So, I think we should change the test rather than removing the limitation. WDYT?
Bug 1966551 Comment 1 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Oh, [the test expects that another synthesized `eMouseMove` should happen when `ePointerOut` is fired by a synthesized `eMouseMove`](https://searchfox.org/mozilla-central/rev/e24d8f4dd564d9fa0beed22224db1d153c22d95b/testing/web-platform/tests/pointerevents/pointerevent_pointerout_no_pointer_movement.html#48-49,52,58). [However, we do not allow that for preventing infinite reflow loop](https://searchfox.org/mozilla-central/rev/e24d8f4dd564d9fa0beed22224db1d153c22d95b/layout/base/PresShell.cpp#6004-6008). I think that this limitation is reasonable. That could cause infinite flickering and/or making a clickable element unavailable. So, I think we should change the test rather than removing the limitation. WDYT?