Teams for Mac looses focus when switching between spaces
1. have multiple Spaces activated on a Mac,
2. move to a different Space than the one where Teams is located and
3. switch back to Teams suing Cmd+Tab,
Teams looses focus, i.e. the three circles in the upper left corner and the search field are both greyed out, you can not continue writing in the chat window and none of the keyboard shortcuts are working. You have to press in the Teams window using the mouse to get focus back. This does not happen when switching between Teams and other apps within the same Space. (However, if you 1. move to a different space and then 2. switch to another app in the same Space as Teams and finally 3. switch to Teams using cmd+tab, Teams still won't get focus until you select the Teams window with the mouse.)
When switching bac to Teams from another app, the application looses
If Teams is fullscreen, then just switches to a blank screen!
Think this item I posted might be related to this (when screen sharing): https://microsoftteams.uservoice.com/forums/908686-bug-reports/suggestions/42810881-teams-macos-toolbar-switches-spaces-when-sharing
TIP : To get around the bug, you can disable this setting:
"Turn on new meeting experience (New meetings and calls will open in separate windows. Requires restarting Teams.)"
Tony G commented
So as mentioned by Mike below, this bug, 41913151 and 41965591 are all same/similar. Could they all be merged or marked as dupes to get focus on the issue please? As mentioned in one of the others, this is an accessibility issue and really needs addressing as it is really annoying.
It should be as simple as removing focus from the notifications window.
Mike Kormendy commented
This appears to be similar/same as this: https://microsoftteams.uservoice.com/forums/908686-bug-reports/suggestions/41913151-cmd-tab-doens-t-go-to-teams-application
Ralf Richtsteiger commented
Can confirm both behaviors with current version 1.3.00.30874 (updated yesterday): lost focus but more frustrating is the missing teams window if you are on another space. Annoying.
And I think this issue needs more attention because there are a lot of similar issues that are related. For instance:
Chris Jones commented
I'm really having have a hard time with this one. Like many others I use Teams as a fullscreen app and use spaces extensively. Having to go back and forth between the mouse and keyboard is really frustrating.
The other part of this that seemed to have changed in the latest version (1.3.00.28778) is when using Command+Tab to switch from another app to Teams, I don't see any Teams window. I have to click on the Window menubar and select the correct window in order to see it. There is another Window called "Microsoft Teams Notification" that seems to always take focus (but there is nothing there).
This is absolutely maddening and terrible.
Yes, this problem is so annoying. I found there is always an invisible teams window (within the application) designed to render notifications alongside the main window which holds the chat interface. I've been constantly frustrated by this invisible window taking focus instead of the main window.
I'm chatting with someone and mid conversation need to alt-tab to another application to check on something. When I command-tab back to the application, the app looks like it has focus and the cursor is blinking in the chat input box, but I can't type anything.
As it turns out, the Teams app has focus but it's actually this invisible notifications window which has focus. I can click anywhere on the teams window to give the main window focus and can continue my conversation.
How hard is it to ensure the main window gets focus and perhaps only give this notifications window focus when a notification occurs?
An even better solution would be to remove this window entirely and use the built in notifications system offered by MacOS so that OS level features like "Do not disturb" work as you would expect.
I am also seeing this issue. It seems that the "Microsoft Teams Notification" window is the active window, not the client. This is also apparent when the client is in full screen mode. Navigating to the client does not make it the active window.