Imported from the Apple Support Forums via the Wayback Machine 🔗
Hello.
If you use traditional cmd+tab, you'll notice that whatever window (in an app) you've last been on will be the one you cmd+tab to.
For example, I have three Safari windows open, window 1, 2, and 3. I am looking at window 2 right now. I cmd+tab to an app on a different Space, and then cmd+tab back to Safari. Window 1, 2, OR 3 might now have focus. There's no way to predict it. Contrast to traditional cmd+tab, in which window 2 would have focus (since it's the last window focused when I cmd-tabbed away).
An interesting consequence is that if you have several app windows open in different spaces, you *cannot predict which space you will be transported to when you cmd-tab to that app!*
Am I missing something? Is there a switch I forgot to check?
Imported from the Apple Support Forums via the Wayback Machine 🔗
Bump for great justice.
0
jbertolacci·
Imported from the Apple Support Forums via the Wayback Machine 🔗
Having the same annoying trouble here as well. If I command-tab to an application in another space, when I command-tab back to the original app, the window I had just been working in is now buried and I need to cycle through each to find it again. Interestingly, the window I was previously working in is still receives keyboard input like it is in focus, but it has been cycled visibly behind other windows.
0
PaulB·
Imported from the Apple Support Forums via the Wayback Machine 🔗
Still happening now after the 10.5.2 update.
0
Randall Farr·
Imported from the Apple Support Forums via the Wayback Machine 🔗
I was really hoping that this problem would get fixed this time around. Has there been a bug report filed?