Chrome is switching spaces to wrong window via command-tab
Reported by
terry27...@gmail.com,
Oct 23
|
|||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/70.0.3538.67 Safari/537.36 Steps to reproduce the problem: 1. Create two spaces in MacOS. Create two Chrome windows (Chrome1 and Chrome2) and move one to the second space. Have a third party app open in the first space (for this example, I will use Calendar). 2. Go back to the first space and click on Chrome1. 3. Use the App Expose shortcut in MacOS (mine is three finger swipe down) to switch to Chrome2. Move spaces back and select Chrome1, such that is in focus (go to a website or something). 4. Command-tab to Calendar (or other third party app), then command tab back to Chrome. Note that it will switch Spaces to the other Chrome window in the second space(Chrome2) despite a) it should have switched to Chrome1 because that was the most recent window in the space. b) The setting "When switching to an application, switch to a space with open windows for the application" has no effect on this; Chrome will switch spaces (and to the wrong window), even when the user explicitly set against this behavior in the System Preferences, and even if the user hadn't, this behavior would still be wrong. Also note, this only happens when switching within the same space as Chrome1. When coming from a third space with another third party app, it will switch to the correct, most recent Chrome window, making this doubly unpredictable and frustrating. What is the expected behavior? Command tab on Mac will always go back to the most recent window for Chrome, and if "When switching to an application, switch to a space with open windows for the application" is unchecked, the most recent window in that space. Note before step 3: Observe that using command-tab to switch between Calendar and Chrome 1 works as expected, and if one is in the second space and command tabs to Calendar and then back to Chrome, it will follow the expected behavior depending on whether "When switching to an application, switch to a space with open windows for the application" is checked in Mission Control settings. What went wrong? Using App Expose somehow breaks Chrome's sense of which is the most recently focused Window, and switching to a window in another space with App Expose will cause Chrome to always switch to that window when command-tabbing to Chrome, even if it was not the most recently focused Window. Did this work before? N/A Chrome version: 70.0.3538.67 Channel: stable OS Version: OS X 10.14.0 Flash Version:
,
Oct 23
,
Oct 24
Here's a screencast I recorded: https://youtu.be/RkanPBg_Mgk For this example, I have ""When switching to an application, switch to a space with open windows for the application" unchecked but the behavior is still present (and still wrong) even if it were checked, as it ignores the open window in the current space. I have used the latest Canary build and the latest Chrome build; both exhibit this behavior. Electron apps like VSCode do not exhibit it, and neither do Firefox or Safari. The terminal command "defaults write com.apple.dock workspaces-auto-swoosh -bool NO" completely turns off auto swooshing, which fixes this, and causes Chrome to switch to the correct window consistently. However, this is undesirable as now App Expose doesn't work for windows in other spaces for all apps.
,
Oct 24
Forgot: a "killall Dock" is necessary after the terminal command to reboot the window server.
,
Oct 24
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Oct 26
Thanks for the detailed screencast. I can reproduce it now. I can't reproduce it with MacViews disabled in Chrome Stable 70, so it is probably MacViews related.
,
Oct 26
Routing to sdy@ for spaces/fullscreen.
,
Nov 1
,
Nov 1
,
Nov 8
,
Dec 11
|
|||||||||
►
Sign in to add a comment |
|||||||||
Comment 1 by meh...@chromium.org
, Oct 23