forked from chromium/chromium
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
chromeos: give priority to certain targets during event dispatch
Currently if an event has an explicitly set target (as happens in mus) we potentially have two paths: 1. Try FindTargetInRootWindow() and if that returns non-null, than that becomes the initial target. 2. Walk up from target returning the first ancestor with an event_targeter. We then most likely (but not always) call FindTargetForEvent() to reevaluate who should be the target. Problem is, if the target is not the root, then we skip the targets that take priority. For example, if there is capture there is no guarantee the capture window will be returned. This patch makes it so that if there is a capture window, mouse pressed handler, or gesture touch lock handler, then it takes priority and gets the event. This makes mus match classic behavior. This fixs behavior where during window resize the size of the window might bounce around. The bouncing happens if the window with capture doesn't get the event. BUG=none TEST=none Change-Id: I519a9126f8aada86498e13900dd0c499312eaae4 Reviewed-on: https://chromium-review.googlesource.com/643948 Reviewed-by: Sadrul Chowdhury <sadrul@chromium.org> Commit-Queue: Scott Violet <sky@chromium.org> Cr-Commit-Position: refs/heads/master@{#498703}
- Loading branch information
Scott Violet
authored and
Commit Bot
committed
Aug 31, 2017
1 parent
868f062
commit 1d58e1c
Showing
14 changed files
with
219 additions
and
62 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.