The logic for sending NS_MOUSE_ENTER/EXIT in Cocoa widgets is pretty complicated. This is a bug for an edge case that we know is broken. It is unlikely that this edge case will cause any actual problems, but we wanted to document it here. If you have a page with an iframe in the middle of it (which has its own ChildView native widget) and you place a window from another app such that the windows edge is exactly along the edge of the iframe, then you move your mouse from the iframe to the overlapping window, the iframe's superview will incorrectly receive an NS_MOUSE_ENTER event.
fixed by bug 355102 which removes the algorithm that could get us into this situation and replaces it with a more robust algorithm
Status: NEW → RESOLVED
Last Resolved: 12 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.