diff options
| author | sadrul@chromium.org <sadrul@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2014-02-26 05:31:43 +0000 |
|---|---|---|
| committer | sadrul@chromium.org <sadrul@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2014-02-26 05:31:43 +0000 |
| commit | d05cf2f1ab93b70f152cb673a102ef2d0e125a72 (patch) | |
| tree | db52c14fa05e9c39faefde5a0ad2eff52266221c /ash/wm/maximize_mode/maximize_mode_window_manager.cc | |
| parent | 1b71f74af8a09558576bba939c9726cc7b4b7c4d (diff) | |
| download | chromium_src-d05cf2f1ab93b70f152cb673a102ef2d0e125a72.zip chromium_src-d05cf2f1ab93b70f152cb673a102ef2d0e125a72.tar.gz chromium_src-d05cf2f1ab93b70f152cb673a102ef2d0e125a72.tar.bz2 | |
aura: Make sure WindowEventDispatcher only dipatches events to in it.
If an event arrives at a WindowEventDispatcher targeted to a Window not owned by
it, then stop the event-dispatch at this dispatcher, and dispatch the event from
the correct dispatcher instead.
To explain with an example:
* There are two WindowEventDispatchers A and B.
* Window W is in A.
* An event comes in (from the native platform) to dispatcher B.
* The event is targeted at W (because it has capture, or because it has focus
etc.)
* Instead of dispatching the event to W from B, stop the event-dispatch in B
and dispatch the event to W from A instead.
BUG=346808
R=oshima@chromium.org, sky@chromium.org
Review URL: https://codereview.chromium.org/180173004
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@253368 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'ash/wm/maximize_mode/maximize_mode_window_manager.cc')
0 files changed, 0 insertions, 0 deletions