User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.0.1) Gecko/20030306 Camino/0.7 Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.0.1) Gecko/20030306 Camino/0.7 If I place the mouse pointer over a link with a :hover style set, then take the focus away from Mozilla (e.g. by pressing Cmd-Tab), the link the mouse was over keeps its highlighting, even if I subequently move the pointer away from the link. The highlighting only vanishes if I give Mozilla the focus and move the mouse. Reproducible: Always Steps to Reproduce: 1. Open <http://svnbook.red-bean.com/html-chunk/> 2. Place mouse pointer over a link. 3. Press Cmd+Tab 4. Move mouse pointer away from link Actual Results: Link gets blue background highlighting at step 2, and doesn't lose it in step 3 or 4. Expected Results: Highlighting should have disappeared on step 3, or maybe step 4. This may be connected to bug#20022 -- presumably Mozilla isn't getting mouse-movement events when it's in the background.

Ben, Do you still see this? WFM Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8a) Gecko/20040509 Firefox/0.8.0+ 10.3.3

Confirmed using Mozilla-Mac/1.7b. Should sending Mozilla into the background cancel all hover effects? Does Mozilla know it’s been backgrounded via this method?

This requires fixing the Mac widget code to send the correct NS_MOUSE_EXIT and NS_MOUSE_ENTER events when the user uses Command-Tab.

But we need to be careful to fire them only if the mouse is in the window. (The time to fire them should correspond to when we currently fire NS_ACTIVATE and NS_DEACTIVATE.)

*** Bug 329802 has been marked as a duplicate of this bug. ***

See also bug 6582 and bug 270872.

It's possible bug 331349 fixed this **for Cocoa widgets**.

*** Bug 334682 has been marked as a duplicate of this bug. ***

*** Bug 340853 has been marked as a duplicate of this bug. ***

I thought about doing this when I fixed bug 340592, but decided against it because I didn't want to make too many changes at once, and it wasn't clear that it would be the correct behavior. We do now send NS_MOUSE_ENTER when activating a new window.

FWIW, this still occurs for me using a recent Camino (Version 1.6.6 (1.8.1.19 2008121219)) on Mac OS X 10.5.6.

This is fixed for me in Firefox 48 on OS X 10.11.

Verified using Firefox 48.0.1 on OS X 10.11.6.