1650657 - Pointer gets "stuck" when closing tab while moving mouse

Status: RESOLVED FIXED

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

Description

[Asif Youssuff]

From: https://www.reddit.com/r/firefox/comments/hllbab/firefox_78_cursor_symbol_gets_stuck_when_closing/

Problem: When you move your mouse and close one tab with ctrl+w and Firefox switches to a previous tab, your cursor symbol gets stuck (doesn't switch to index finger pointing when hovering over links for example) until you right click context menu and hover it, or hover over url bar.

How to replicate: Open reddit.com, open a comment thread into another tab, close this tab with ctrl+w WHILE moving your cursor to any direction steadily on the webpage (not urlbar), your cursor is now stuck into one symbol, regardless if you hover over a hyperlink.

Also reported by:

https://github.com/Robbendebiene/Gesturefy/issues/514
https://github.com/marklieberman/foxygestures/issues/318

Regressed by:

Bug 1607375 - Generate mouse exit event to old remote target when the mouse event is moving to another remote target; r=hsivonen,smaug

If a mouse is over a remote target A, and then moves to remote target B, we'd deliver the event directly to remote target B after the moving, A would never get notified that the mouse left. And A would synthesizes mousemove event on an incorrect point which then generates an unexpected mouseleave.

Differential Revision: https://phabricator.services.mozilla.com/D67408

Comment 1

[Asif Youssuff]

Edgar,

Can you take a look at this? Your patch in bug 1607375 seems to have regressed behavior for people using gesture add-ons - the issue appears without add-ons, however.

Thanks!

Comment 2

[Edgar Chen [:edgar]]

There is a similar bug 1638091 reported in 78. And bug 1635784 fix it.
I believe bug 1635784 would also fix this one.

Did you see the same issue on Nightly? Thanks.

Comment 3

[BugBot [:suhaib / :marco/ :calixte]]

Set release status flags based on info from the regressing bug 1607375

Comment 4

[Asif Youssuff]

Edgar, reporting user says that it is not reproducible in Nightly.

Comment 5

[Ryan VanderMeulen [:RyanVM]]

Sounds like this was fixed by bug 1607375.

Comment 6

[Asif Youssuff]

Ryan, I don't understand how this bug could have been fixed by bug 1607375 - that was the regressing bug.

Comment 7

[Ryan VanderMeulen [:RyanVM]]

Sorry, that should have been bug 1635784. I set the dependencies correctly at least :-)

Comment 8

[Edgar Chen [:edgar]]

(Update status prorperly: given that this is a generic bug, not fission-only)

Comment 9

[Ryan VanderMeulen [:RyanVM]]

Bug 1635784 looks like more than we'd want to uplift to an ESR release. Is there a more targeted fix we can/should land on ESR or should we wontfix this bug there?

Comment 10

[Edgar Chen [:edgar]]

(In reply to Ryan VanderMeulen [:RyanVM] from comment #9)

Bug 1635784 looks like more than we'd want to uplift to an ESR release. Is there a more targeted fix we can/should land on ESR or should we wontfix this bug there?

Yeah, bug 1635784 contains some fission-specific changes. Part 3 and part 4 patches of bug 1635784 are generic changes and should be enough for this issue.