Bug 11739 - onMouseOver and onMouseOut incorrectly triggered on URL inside table in Safari
Summary: onMouseOver and onMouseOut incorrectly triggered on URL inside table in Safari
Status: RESOLVED WORKSFORME
Alias: None
Product: WebKit
Classification: Unclassified
Component: WebCore Misc. (show other bugs)
Version: 419.x
Hardware: Mac (PowerPC) OS X 10.4
: P2 Normal
Assignee: Nobody
URL: http://www.k12.com
Keywords:
Depends on:
Blocks:
 
Reported: 2006-12-01 17:53 PST by Micah S. Cox
Modified: 2006-12-02 05:33 PST (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Micah S. Cox 2006-12-01 17:53:54 PST
The web site www.k12.com contains a table of URLs used as menu headers.  When the mouse floats over the URL header, the onMouseOver event displays a menu.  When the mouse moves off of the URL, the onMouseOut closes the menu.  In Firefox and Explorer this works fine.  In Safari the menu opens and closes repeatedly as the mouse moves over the menu header.  Both events are being triggered.  When the mouse is still, the menu is closed.  I was only able to get the menu to stay open 1 time, but as soon as the mouse was moved to select an item, the menu closed.  The problem may be with onMouseOut.  It doesn't seem to know when it's truly off of the intended object.
The web site www.k12.com contains a table of URLs used as menu headers.  When the mouse floats over the URL header, the onMouseOver event displays a menu.  When the mouse moves off of the URL, the onMouseOut closes the menu.  In Firefox and Explorer this works fine.  In Safari the menu opens and closes repeatedly as the mouse moves over the menu header.  Both events are being triggered.  When the mouse is still, the menu is closed.  I was only able to get the menu to stay open 1 time, but as soon as the mouse was moved to select an item, the menu closed.  The problem may be with onMouseOut.  It doesn't seem to know when it's truly off of the intended object.

Safari Version 2.0.4 (419.3)
Comment 1 Alexey Proskuryakov 2006-12-02 05:33:04 PST
I can reproduce this with shipping Safari, but the problem appears to have been already fixed in nightly builds: <http://nightly.webkit.org>.