diff options
author | jcivelli@chromium.org <jcivelli@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2010-08-11 06:44:38 +0000 |
---|---|---|
committer | jcivelli@chromium.org <jcivelli@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2010-08-11 06:44:38 +0000 |
commit | 494f5c479d1c61ecfb72ec1e0af89dd8e363d395 (patch) | |
tree | 2fef3beadf58d7c91dd74e326840f5a1cee38649 /views/window/window.h | |
parent | 603e195332575bbe0fd60ba86041e96516372522 (diff) | |
download | chromium_src-494f5c479d1c61ecfb72ec1e0af89dd8e363d395.zip chromium_src-494f5c479d1c61ecfb72ec1e0af89dd8e363d395.tar.gz chromium_src-494f5c479d1c61ecfb72ec1e0af89dd8e363d395.tar.bz2 |
Making window.focus() work in Chrome.
A patch on the WebKit side https://bugs.webkit.org/show_bug.cgi?id=43542
ensures we get the correct notification when window.focus()/blur() is called.
This CL makes the browser active/unactive in response to the focus/blur message.
BUG=29643
TEST=Visit gmail. Open an IM conversation window and pop-it out.
Focus the browser (so the IM window is in the back). Click on the person name in the IM section of gmail.
The conversation window should be brought back to the front.
Repeat but this time minimize the conversation window.
Review URL: http://codereview.chromium.org/3060045
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@55678 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'views/window/window.h')
-rw-r--r-- | views/window/window.h | 6 |
1 files changed, 5 insertions, 1 deletions
diff --git a/views/window/window.h b/views/window/window.h index af1dc70..1d5ffea 100644 --- a/views/window/window.h +++ b/views/window/window.h @@ -93,9 +93,13 @@ class Window { virtual void DisableInactiveRendering() = 0; #endif - // Activate the window, assuming it already exists and is visible. + // Activates the window, assuming it already exists and is visible. virtual void Activate() = 0; + // Deactivates the window, making the next window in the Z order the active + // window. + virtual void Deactivate() = 0; + // Closes the window, ultimately destroying it. This isn't immediate (it // occurs after a return to the message loop. Implementors must also make sure // that invoking Close multiple times doesn't cause bad things to happen, |