1938528 - Enable the new mouse/pointer boundary behavior in release

Status: RESOLVED FIXED

(Core :: DOM: UI Events & Focus Handling, task)

Description

[Hsin-Yi Tsai (she/her)[:hsinyi]]

We enabled the behavior in nightly/early-beta for months.
We didn't ship the new behavior to release back than, because of the alignment with Chrome at that time , see bug 1875424 comment 3. But it looks like Chrome have the same behavior on Release/Stable and Experimental channels, according to the wpt results. We can try to let the new behavior riding trains to release.

Comment 1

[Masayuki Nakano [:masayuki] (he/him)(JST, +0900)]

Indeed. Let's enable the new behavior.

Comment 2

[Masayuki Nakano [:masayuki] (he/him)(JST, +0900)]

(Oddly, I don't find the change which enabled the new behavior in the release channel in their repository...)

Comment 3

[Masayuki Nakano [:masayuki] (he/him)(JST, +0900)]

Attachment: Bug 1938528 - Enable new mouse and pointer boundary event behavior in the release channel r=smaug!,#dom-core

In bug 1875424, I disabled the new behavior because of compatibility with
Chrome. However, it seems that they shipped the new feature. So, following
them is better for compatibility with them.

Comment 4

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/76ee1ce0de55
Enable new mouse and pointer boundary event behavior in the release channel r=smaug

Comment 5

[agoloman]

https://hg.mozilla.org/mozilla-central/rev/76ee1ce0de55

Comment 6

[Ryan VanderMeulen [:RyanVM]]

Is this something we should call out in the Fx135 relnotes? Please add a relnote-firefox request if so.

Comment 8

[Masayuki Nakano [:masayuki] (he/him)(JST, +0900)]

Release Note Request (optional, but appreciated)
[Why is this notable]: This changes traditional behavior of mouseenter, mouseleave, pointerenter and pointerleave events when the last mouseover or pointerover event target is removed.
[Affects Firefox for Android]: Yes
[Suggested wording]: Even after the last event target of mouseover or pointerover is removed from the DOM tree, the last deepest mouseenter and pointerenter target which is still connected is stored correctly. Thus, the ancestor elements of the removed target will receive mouseleave and pointerleave events without redundant mouseenter and pointerenter events.
[Links (documentation, blog post, etc)]: The last paragraph of https://w3c.github.io/pointerevents/#dfn-fire-a-pointer-event

Comment 9

[Ryan VanderMeulen [:RyanVM]]

Added to the Fx135 relnotes.