187045 - onMouseOver and onMouseOut events not recognized when scrolling

Status: VERIFIED DUPLICATE of bug 50511

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

Description

[David C. Holley]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.2.1) Gecko/20021130
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.2.1) Gecko/20021130

It appears that the onMouseOver and onMouseOut events are not recognized when
the browser window is scrolled. This problem can occurr if the user has a mouse
that features a scroll wheel. I discovered the problem while testing a
JavaScript function that I am developing. (A sample page is available upon
request.) I have confirmed that the script functions properly with Netscape 7,
IE 6 and Opera 6.05.

Reproducible: Always

Steps to Reproduce:
Please contact me via email for the HTML file that I am developing as it is
neccessary to reproduce the bug.
1. Once Mozilla displays the before mentioned bug, move the mouse over the cells
in the table. As the mouse moves over the cells, the cells will highlight and
unhighlight.

2. Move the mouse over a cell to cause it to highlight.

3. Without physically moving the position of the mouse, scroll the window using
the scroll wheel on the mouse. The previously highlighted cell will remain
highlighted.
Actual Results:  
The highlighted cell remains highlighted until the mouse is physically moved.

Expected Results:  
Mozilla should have recognized that while the mouse was not physically moved,
the relative position between the mouse and the cell changed. Mozilla should
have fired the onMouseOver and onMouseOut events.

Comment 1

[David C. Holley]

Attachment: Sample HTML page demonstrating the onMouseOver and onMouseOut events

The attached HTML page includes a JavaScript function that highlights and
unhighlights the cells in the table as the mouse moves over them. I have
confirmed that the page functions properly under IE6, Netscape7.0 and Opera
6.05.

Comment 2

[R.K.Aa.]

see also bug 78765 and spinoffs

*** This bug has been marked as a duplicate of 50511 ***

Comment 3

[Trix Supremo]

verifying dupe