bugzilla.mozilla.org will be intermittently unavailable on Saturday, March 24th from 16:00 until 20:00 UTC.

OnMouseOut fires immediately after OnMouseOver




Event Handling
16 years ago
9 years ago


(Reporter: Tom Welch, Unassigned)


Windows XP

Firefox Tracking Flags

(Not tracked)



(1 attachment)



16 years ago
When moving the mouse over the contents of the document, the OnMouseOut events
for each object are fired after a very short delay after OnMouseOver.  This
happens even though the mouse is still over the element being hovered.

This apparently has many side effects.  The primary one being that the status
bar changes to "Document: Done (x.xxx secs)" while hovering over a hyperlink.

Quite possibly, this also causes menu items to highlight and unhighlight
immediately in the program's menu system.

Web pages that use the onMouseOver and onMouseOut events to toggle item styles
or states behave horribly, from flicker to failure.

Comment 1

16 years ago
I've had these two functions work correctly. Is there a specific page(s) that
you see this problem on? 
this is probably the same as bug 139348...
Please attach a testcase?  Are you sure you're not seeing mouseouts on #text nodes?

Comment 4

16 years ago
Actually, this problem is seen on any webpage.  However, I discovered that it
only happens when the browser window is in the secondary display of a
multi-monitor configuration.  And perhaps it only happens when the secondary
display is to the left of the primary because in this case, the screen
coorditates are negative numbers.

To reproduce this bug:

1. Configure your system for multiple monitors
2. Make the right monitor the primary
3. Open Mozilla
4. Drag the Mozilla window to the secondary display
5. Open any webpage
6. Hover the mouse over any hyperlink
7. Notice that the status bar changes to the URL and immediately back to
"Document Done"
8. Load a page with any roll-over effect.
9. Notice that the effect is toggled on and immediately toggled off.
To events, ccing bryner.
Assignee: asa → joki
Component: Browser-General → Event Handling
Ever confirmed: true
QA Contact: asa → rakeshmishra

Comment 6

16 years ago
I think I'm seeing this in post-1.2b FizzillaCFM builds, as well. This breaks
mouseovers, and is more severe than trivial.


16 years ago
QA Contact: rakeshmishra → trix

Comment 7

15 years ago
Is this bug related to bug #185889 that John Keiser have been working on
recently?  He had his hand full on so many similiar mouseover and mouseout bugs.
 Please take a look at it and see if this is not a related bug.  Thanks....

Comment 8

15 years ago
Doesn't sound the same to me.  Does it still happen in a recent build?

Comment 9

15 years ago
This problem is extremly severe in Komodo (we're updating moz for our next
version), and I just started to look into it today.  I've read through a ton of
the mouseout related bugs, not realy finding that it is completely resolved.  

I just downloaded today's latest moz from trunk, built it (win2k), and can still
see the problem (non-komodo build).  An interesting thing though, if I drag a
xul element, for instance in the bookmarks sidepanel, then mouseovers are fine.
   If I then simply click in the browser pane, then mouseovers fail (mouseout
being fired).  I can repeat this at will.  Simply clicking on a xul element to
set focus onto it does not fix mouseover/out stuff, something must be dragged.  

After discovering that, I did the same in Komodo (moz from feb 20 trunk), and am
able to fix mouseovers by dragging something.

Comment 10

15 years ago
ignore my last comment on this, thought I'd removed my patches before building,
turns out I didn't, I now think it's one of my patches that are messing things
up for me.
Tom, this problem may be fixed, can you confirm whether it is still there?

Comment 12

15 years ago
This relates to version 1.3:

I can confirm Tom Welch's comment #4.  I'm running 4 monitors on WinXP, and this
behaviour appears in only one of them - the one left of the primary monitor.  If
I set the primary monitor to be the leftmost, all is fine.

Similar situation occurs with a colleague also on XP.

Another colleague has tried to reproduce the bug with his dual-monitor Linux
system, but all is fine there.

Comment 13

15 years ago
I can also confirm Tom Welch's comment #4, and that this problem exists in 1.4

Mozilla 1.4
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624

The issue only happens on my secondary display (my laptop lcd).  
The browser behaves as it should on the main display (CRT).


Comment 14

15 years ago
Assignee: joki → saari
QA Contact: trix → ian

Comment 15

15 years ago
Created attachment 132181 [details]
mouseout immediately after mouseover on everything(even browsers menus as shown in attachment)

My Computer:
Browser: Firebird 0.6.1

I use 2 monitors on my XP. On main monitor there is no problem. On my secondary
there is. even if i let a link in the browser split over 2 scrren, this link
will work properly on the main monitor, but not on the secondary.

Comment 16

15 years ago
Comment on attachment 132181 [details]
mouseout immediately after mouseover on everything(even browsers menus as shown in attachment)

....but only when secondary monitor is placed left of the primary monitor
instead of normally right.

Comment 17

15 years ago
I can attest to this same problem, only when the monitor is in the negative
pixel range.  I'm running Firebird 0.7 on WinXP, using an ATI Mobility Radeon
7500 driver.

Also, I cannot select any URLs from the Main Address Bar's history drop-down. 
They appear, but when I select one, it just reloads the page I'm currently on.

Again, this only happens when I have the Firebird window open on the secondary
monitor, and the secondary monitor is to the left of the main monitor.  Probably
something to do with being in the negative pixel range?



Comment 18

14 years ago
I can only confirm what others have posted previously. I have a two monitor
setup under Windows XP and if Firefox is on my left screen (which is not my
primary screen), all mouseOver events are immediately followed by mouseOut. Very

Comment 19

14 years ago
Confirming.  Also, having not seen it here, here is a url where you can test it:

Again, if I move the browser to the second monitor, it reports mouseout
immediately after mouseover.  On my primary (right) monitor, this works fine.  I
am not sure if this is Gecko or XP, but it is definately a problem for anyone
running dual-monitors.

Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7b) Gecko/20040328 Firefox/0.8

Comment 20

14 years ago
I'd like to see this bug re-assigned. Will it ever be fixed? This is currently
preventing me from using Moz/Firefox at work where I have a dual monitor setup.
Also, I believe that the severity should be more than "trivial".


Comment 21

14 years ago
Fixed in FireFox 0.9b? 

This bug seems to be fixed in the latest beta release of FireFox. I just
installed it and it works just fine on both my displays, so I assume that some
changes have been made to the code which will make it to the final version of
FireFox and also Mozilla?
Assignee: saari → nobody
QA Contact: ian → events
You need to log in before you can comment on or make changes to this bug.