[Webkit-unassigned] [Bug 3439] mouseover effects can get stuck sometimes due to missing events

bugzilla-daemon at opendarwin.org bugzilla-daemon at opendarwin.org
Sun Mar 19 12:35:34 PST 2006


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


ap at nypop.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
Attachment #7169 is|0                           |1
           obsolete|                            |
   Attachment #7179|                            |review?
               Flag|                            |




------- Comment #13 from ap at nypop.com  2006-03-19 12:35 PDT -------
Created an attachment (id=7179)
 --> (http://bugzilla.opendarwin.org/attachment.cgi?id=7179&action=view)
proposed fix

Moved the subframe code from MouseEventWithHitTestResults to a function in
FrameView.cpp.

Checking for inDocument() changes the results of one of the included tests to
not match Firefox and WinIE - they seem to dispatch mouseOut events to removed
nodes. OTOH, as mentioned above, it changes the results for IFRAME to match
Firefox. Seems better this way, but I may be missing something.

There is already a ref for targetNode as it is assigned to d->underMouse. But
we actually needed a ref for "this", added now. The difference between
d->underMouse and d->oldUnder looks ugly; I don't really understand it.

Other changes, as discussed on IRC: added a helper for prepareMouseEvent,
removed prevMouseX/prevMouseY, moved the new data members to FrameViewPrivate.

Didn't address the fact that an additional mouse move is needed to mouseOut
events to fire after an element under mouse is removed - will probably fit in
bug 4117 better.


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