[Webkit-unassigned] [Bug 7701] Using Javascript & CSS hovers sometimes doesn't un-hover
bugzilla-daemon at opendarwin.org
bugzilla-daemon at opendarwin.org
Fri Mar 10 12:49:41 PST 2006
http://bugzilla.opendarwin.org/show_bug.cgi?id=7701
opendarwin.org at mitzpettel.com changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |opendarwin.org at mitzpettel.co
| |m
------- Comment #3 from opendarwin.org at mitzpettel.com 2006-03-10 12:49 PDT -------
This test case is a great example of what the comment in
FrameView::dispatchMouseEvent() says about not caching the old mouse-over node.
In this case, as the mouse enters "Three", the code tries to calculate which
node the mouse was previously in, but while doing this, first of all it updates
the document's layout applying to the already-updated hover states. According
to the new layout, the previous mouse position was in "Four", so "Three Four"
is sent a bogus mouse out event, and "One Two" never gets one.
--
Configure bugmail: http://bugzilla.opendarwin.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
More information about the webkit-unassigned
mailing list