[Webkit-unassigned] [Bug 6821] New: Fix for 5983 will not always update hover correctly.

[bugzilla-daemon at opendarwin.org]

http://bugzilla.opendarwin.org/show_bug.cgi?id=6821

           Summary: Fix for 5983 will not always update hover correctly.
           Product: WebKit
           Version: 420+ (nightly)
          Platform: Macintosh
        OS/Version: Mac OS X 10.0
            Status: NEW
          Severity: normal
          Priority: P2
         Component: XML DOM
        AssignedTo: webkit-unassigned at opendarwin.org
        ReportedBy: mjs at apple.com


The fix for http://bugzilla.opendarwin.org/show_bug.cgi?id=5983 sometimes won't
update properly update hover when the current hover node is removed. In
particular, if you remove a node in the normal flow such that a sibling is now
positioned under the mouse, the sibling won't properly get hover. Instead of
doing the weird walk up the render tree, it might be better to just setHover(0)
and set a 0-delay timer to fire a mouse event at the current mouse position.

Another possibility that would catch all kinds of dhtml-driven hover changes
would be to send a fake mouse event at the current mouse position every time we
update rendering or lay out or whatever. But this runs the risk of hurting
DHTML performance, according to hyatt. We'd need some way to measure.


-- 
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.