Summary: Previously, Pointer Events defined that pointer boundary events
such as `|pointerover|`, `|pointerenter|`, `|pointerout|` and
`|pointerleave|` are fried as a preprocessing of dispatching a pointer
event. E.g., when the element underneath the pointer is changed by a
layout change, e.g., by a DOM mutation, a style change or a scroll,
pointer boundary events should have been fired before dispatching next
`|pointermove|`, `|pointerdown|` or `|pointerup|`, etc. However, now,
the spec defines that the pointer boundary events should be fired as
soon as possible (but allowed to dispatch after a tick). Therefore, we
need to change our implementation for conforming to the new spec.
Bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1966551
Specification:
https://w3c.github.io/pointerevents/#boundary-events-caused-by-layout-changes
Platform coverage: Only desktop due to bug 1633450
<https://bugzilla.mozilla.org/show_bug.cgi?id=1633450>
Preference: |dom.event.pointer.boundary.dispatch_when_layout_change|
DebTools bug: N/A
Other browsers: Chrome already shipped the new behavior, Safari does not.
web-platform-tests:
https://wpt.fyi/results/pointerevents/pointerevent_pointerout_no_pointer_movement.html?label=experimental&label=master&aligned
<https://wpt.fyi/results/pointerevents/pointerevent_pointerout_no_pointer_movement.html?label=experimental&label=master&aligned>
--
Masayuki Nakano<[email protected]>
Working on DOM, Events, editor and IME handling for Gecko
--
You received this message because you are subscribed to the Google Groups
"[email protected]" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion visit
https://groups.google.com/a/mozilla.org/d/msgid/dev-platform/128c558e-8c65-4c66-9f82-7c48be3ee278%40d-toybox.com.
