Use NSTrackingArea for mouse event targeting

RESOLVED FIXED in mozilla8



Widget: Cocoa
6 years ago
6 years ago


(Reporter: mstange, Assigned: mstange)


Mac OS X
Dependency tree / graph
Bug Flags:
in-testsuite +

Firefox Tracking Flags

(Not tracked)



(1 attachment)



6 years ago
Created attachment 549374 [details] [diff] [review]

We could have done this ever since we dropped 10.4 compatibility. I don't know why I didn't think of this sooner.

The current mouse move event targeting setup has two drawbacks:
 1. It's unnecessarily CPU-intensive because we traverse all windows on the
    screen on every mouse move, even if we're not the active application, and
    even if all our own windows are hidden behind other apps' windows.
 2. The system wide mouse move event monitor might be the reason for
    bug 611068. (If it's not, the mouse down event tap is.)

We're taking these measures because [window setAcceptsMouseMoveEvents:YES] will always send the event to the current first responder, no matter which window the mouse is actually over. It also doesn't by default send events when our app is inactive.

Well, NSTrackingArea changes all that and actually behaves like you'd expect it to: Mouse move events are always and only sent to the tracking area under the mouse, and you can even specify that you'd like to get events regardless of app activation status (NSTrackingActiveAlways).
NSTrackingAreas have one imperfection: You don't get a mouse enter event if the mouse is already inside the area that's being created. But that's not so bad because we can correct the mouse enter state as soon as the mouse moves.

Most of this patch is very straightforward: There's one tracking area per window, and it gets recreated whenever the window size changes. As for the rest:
 - The sendEvent override on PopupWindow has been unnecessary ever since we
   dropped 10.4 compatibility. I've extensively tested this ages ago but never
   got around to filing a bug about it. However, now it's even actively
   harmful because it routes mouse events to the first responder, so they
   don't get to the tracking area. That's why I'm removing it.
 - The testing story is tricky. Synthesizing mouse moves and getting tracking
   area events seems impossible, so the test simulates the expected events.
   I've also removed those parts of the test that sent mouse events to windows
   that are not under the mouse because those cases don't occur with tracking

I've tested this patch on 10.6 and 10.7 and couldn't find any regressions. I've gone through all the bugs in the blame range of the code I'm removing.
This build contains the patch:
Attachment #549374 - Flags: review?(joshmoz)


6 years ago
Attachment #549374 - Flags: review?(joshmoz) → review+

Comment 1

6 years ago
This patch replaces some of the most unfortunate code in Cocoa widgets. Thanks for doing this!

Comment 2

6 years ago
Whiteboard: [inbound]

Comment 3

6 years ago
I've backed this out to see whether it's responsible for the 60% Trace Malloc MaxHeap increase that can be seen on
Whiteboard: [inbound]

The backout changeset has not made it to m-c yet.
Target Milestone: --- → mozilla8

Comment 5

6 years ago
And relanded on inbound because it wasn't responsible. (Bug 668195 is.)
Last Resolved: 6 years ago
Resolution: --- → FIXED
The backout made it to m-c:
Resolution: FIXED → ---
Last Resolved: 6 years ago6 years ago
Flags: in-testsuite-
Resolution: --- → FIXED


6 years ago
Flags: in-testsuite- → in-testsuite+


6 years ago
Depends on: 678691
You need to log in before you can comment on or make changes to this bug.