diff options
author | ananta@chromium.org <ananta@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2013-10-08 21:23:09 +0000 |
---|---|---|
committer | ananta@chromium.org <ananta@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2013-10-08 21:23:09 +0000 |
commit | fb3bf2d6fb8bc7da2cdf0bd5798908672a9697fb (patch) | |
tree | 81d8274ad66c773cce2ce4c0eb5f4310bd1f3385 /content/browser/loader/throttling_resource_handler.cc | |
parent | d51597d954013788312cf832478bd8dab9d8090b (diff) | |
download | chromium_src-fb3bf2d6fb8bc7da2cdf0bd5798908672a9697fb.zip chromium_src-fb3bf2d6fb8bc7da2cdf0bd5798908672a9697fb.tar.gz chromium_src-fb3bf2d6fb8bc7da2cdf0bd5798908672a9697fb.tar.bz2 |
Ensure that in desktop AURA if the dummy container window does not inadvarently get activated because of a sibling
window (modal window) getting destroyed.
We should activate its child window which hosts the real content in this case.
Added an implementation for the DesktopRootWindowHostX11::InitFocus function to set the focused window in the focus
client. The DesktopRootWindowHostX11 class was setting the focused window in the InitRootWindow function which is early
because the content window being focused is not yet visible.
Fixes bug https://code.google.com/p/chromium/issues/detail?id=303484
BUG=303484
R=sky@chromium.org, sky
TEST=Covered by interactive ui test WindowModalWindowDestroyedActivationTest
Review URL: https://codereview.chromium.org/26081002
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@227593 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'content/browser/loader/throttling_resource_handler.cc')
0 files changed, 0 insertions, 0 deletions