Microsoft Teams windows not managed properly

[blokeley]

Microsoft Teams exhibits strange and very annoying behaviour:

1. If the Teams window is minimised (Win+Ctrl+m), it leaves an empty space with no title, so there is a "ghost" window taking up the space that the Teams window took.

2. When in a call and presenting the screen, the Teams window becomes small and floating, but bug.n still tries to control it like a main window which gets in the way of screen sharing.

Does anyone have a set of config rules to solve these problems?

[joten]

Which version of bug.n and Windows are you using?

1. Although not consistently, I could not reproduce the error with bug.n 9.0.2 (default config) and Windows 10 2004.

2. I could not really test a call and presenting the screen in Teams, but you may set additional rules regarding Microsoft Teams in your Config.ini; e.g. I found the following, which should set the defined windows as floating.

Config_rule=Chrome_WidgetWin_1;Microsoft Teams wird geladen;;1;0;0;1;0;1;
Config_rule=Chrome_WidgetWin_1;Microsoft Teams-Benachrichtigung;;1;0;0;1;0;1;
Config_rule=ADALWebBrowserHost;Bei Microsoft Teams anmelden;;1;0;0;1;1;0;

[blokeley]

Thanks. It seems to me that setting the windows to floating means that they're unmanaged, and I was hoping to manage (tile) them.

[ckeschnat]

I am commenting here because it is related to Microsoft Teams, although a bit different, but:

It seems impossible to tell bug.n to ignore voice/videocall-windows. Not managing the main window works fine, the config_rule for the calls is not working though it seems. Is there any other way besides config_rules to ignore them or am I doing anything wrong?

I tried several config_rules:

Config_rule=Chrome_WidgetWin_1;.*Microsoft Teams;;0;3;1;0;1;0;
Config_rule=Chrome_WidgetWin_1;Name with spaces | Microsoft Teams;;0;1;1;0;1;0;
Config_rule=Chrome_WidgetWin_1;.*;;0;1;1;0;1;0;

After reloading and pressing #-i, this is what I get though: Config_rule=Chrome_WidgetWin_1;Name with spaces | Microsoft Teams;;1;1;1;0;1;0;

[ckeschnat]

Update to my previous Post. I just joined another call and there my config_rules were working. I redacted the names, but maybe those are the issue? I'll redact in another way: not working: "AE-FOo Lalelu | Microsoft Teams" working: "Lala Q1 2021"

So might the dash/minus sign in the first window be an issue? I would think ".*" catches it, but maybe not?

Another Update: I was in the same Team again and this time it worked. Nobody was presenting though, so that might have been the issue.

[joten]

bug.n uses the following to apply rules: If RegExMatch(wndClass . ";" . wndTitle, rule1 . ";" . rule2) And (rule3 = "" Or %rule3%(wndId)) and therewith a Perl-compatible regular expression (PCRE). The pipe (|) may be a problem.

[ckeschnat]

bug.n uses the following to apply rules: If RegExMatch(wndClass . ";" . wndTitle, rule1 . ";" . rule2) And (rule3 = "" Or %rule3%(wndId)) and therewith a Perl-compatible regular expression (PCRE). The pipe (|) may be a problem.

Might be. But for the past week I had been using Teams (even with screen sharing) and had no issue (unmanaged), so I don't have a way to test things right now. Seems to be quite a peculiar application. Should the issue arise again I might try to figure out what exactly happens. That line helps, thanks.

[boorac]

Additionally, when someone messages me on Teams, my cursor stops working correctly and repositions itself to the center of the screen every time the Teams icon in the Taskbar flashes. I have not managed to fix it so far.

EDIT: My problem was different and unrelated to Teams. It turns out that my mouse just followed focus. I turned it off as follows: Config_mouseFollowsFocus=0

[nixfu]

Yet ANOTHER MS Teams issue. It seems on my system that teams is always open on EVERY workspace, unless something else is open on that workspace.