diff options
| author | sail@chromium.org <sail@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2011-01-13 00:45:08 +0000 |
|---|---|---|
| committer | sail@chromium.org <sail@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2011-01-13 00:45:08 +0000 |
| commit | 346fb30b0ee89a94ea203b8e60307e10c5466a56 (patch) | |
| tree | 4f9a1f024ba9f67b2c92f86644c999cb3d9517f6 /chrome/browser/remoting | |
| parent | 678da8d75454e48290b042bfdd4784216aead257 (diff) | |
| download | chromium_src-346fb30b0ee89a94ea203b8e60307e10c5466a56.zip chromium_src-346fb30b0ee89a94ea203b8e60307e10c5466a56.tar.gz chromium_src-346fb30b0ee89a94ea203b8e60307e10c5466a56.tar.bz2 | |
Mac: Don't change active Space when entering or exiting full screen
There are two ways that entering full screen could cause the active Space to change:
1: Assign a default Space to the application. Move the browser window to a different Space. Enter full screen. The new full screen window opens in the default Space instead of the active Space. crbug.com/69454
2: Enter full screen. Press F8 to enter Spaces mode. Move the full screen window to a different Space. Exit Spaces. The Single Window window opens in its original Space instead of the active Space. crbug.com/41693
r60063 fixed the second issue but not the first and it also relied on using private APIs.
This change fixes both issues without using private APIs. Instead we now temporarily set the window's collection behavior to NSWindowCollectionBehaviorMoveToActiveSpace. This prevents the active space from changing.
Patch idea by Bjorn Winckler. See:
https://github.com/b4winckler/macvim/commit/6863b04a52fdb501c6df509635b9b3b3dd062e68
BUG=69454, 41693
TEST=Ran on 10.5 and 10.6. Verified that both bugs were fixed.
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@71276 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'chrome/browser/remoting')
0 files changed, 0 insertions, 0 deletions