diff options
author | sergeyu@chromium.org <sergeyu@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2012-10-29 20:07:35 +0000 |
---|---|---|
committer | sergeyu@chromium.org <sergeyu@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2012-10-29 20:07:35 +0000 |
commit | 30275cedc43837db75c1a2ef8f1c22989388f346 (patch) | |
tree | 7758c807923634a737f2a502069aa67ad2f4e50e /ash/system/bluetooth/tray_bluetooth.cc | |
parent | 89627f9d7fba44faaabee1e41f5f672f2e83cc2e (diff) | |
download | chromium_src-30275cedc43837db75c1a2ef8f1c22989388f346.zip chromium_src-30275cedc43837db75c1a2ef8f1c22989388f346.tar.gz chromium_src-30275cedc43837db75c1a2ef8f1c22989388f346.tar.bz2 |
Revert 164703 - it broke BookmarkBarViewTest8.DNDBackToOriginatingMenu on Chrome OS - Register a separate default ui::EventTarget for Aura (Ash) to ensure that it does not interfere with the
event handling in desktop chrome in Aura.
On Windows 8 in chrome metro mode we have a desktop chrome process
which runs as a server to the viewer process in Metro. Reusing the default EventTarget across both environments
causes desktop chrome to crash as a number of EventFilters registered on the default EventTarget get called twice.
The Ash specific EventTarget is implemented by the Ash::Shell class. The RootWindow in its GetParentTarget implementation
delegates this call to the EventClient implementation if one exists and if not it returns the default Aura::Env interface.
The EventClient interface is implemented by Ash and has been updated to return the default EventTarget via the new method
GetToplevelEventTarget
Fixes bug http://code.google.com/p/chromium/issues/detail?id=158105
BUG=158105
R=ben
Review URL: https://codereview.chromium.org/11314013
TBR=ananta@chromium.org
Review URL: https://codereview.chromium.org/11301024
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@164728 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'ash/system/bluetooth/tray_bluetooth.cc')
0 files changed, 0 insertions, 0 deletions