Eliminate event.target use from TrayEventFilter |
||||
Issue descriptionAfter the switch to mus PointerWatcher will no longer provide an event.target for located events. This code may not even be necessary, as the conditions it is checking for may be handled by the bounds testing code at the bottom of ProcessLocatedEvent(). If we still need it we'll need a way to find the aura::Window target of an event, perhaps similar to WmRootWindowController::FindEventTarget(). (We can get the display from FindDisplayNearest(), then WindowTreeHostManager::GetRootWindowForDisplayId())
,
May 9 2016
PointerWatcher now provides the target widget. Attempting to find it from a screen position doesn't work because the app/client doesn't know the window Z order, even of its own windows.
,
May 23 2016
Bulk verified
,
May 23 2016
bulk verified
,
Feb 26 2018
|
||||
►
Sign in to add a comment |
||||
Comment 1 by bugdroid1@chromium.org
, May 9 2016