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

bugzilla-daemon at opendarwin.org bugzilla-daemon at opendarwin.org
Wed Feb 1 13:50:49 PST 2006


------- Comment #10 from opendarwin.org at mitzpettel.com  2006-02-01 13:50 -------
(In reply to comment #9)
> I bet you also need to cancel the timer if the app loses active status or the
> window loses focus.

In WebKit, hover state isn't reset when either of these happen, so even in the
unlikely event that a deactivate event comes between setting the 0-delay timer
and the timer firing, I don't think it's going to cause any problem.

The other thing I looked at is what happens if the window/app is inactive to
begin with when hoveredNodeDetached gets called. Firefox's inactive app
behavior is the same as Safari's inactive window/app behavior, which is to
freeze the mouse where it was. Setting the timer when inactive (and acting upon
it when it fires) is just what's needed to match Firefox's behavior for this
bug's testcases too.

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