Microsoft Teams: "Doh! Something went wrong..."

[ghost]

Which settings in user.js need to be changed from Microsoft Teams to work?

[crssi]

I would guess:

/* 2404  */ user_pref("dom.indexedDB.enabled", true); // false breaks sites like OWA

[ghost]

I already set this for Outlook Web App to work (https://github.com/ghacksuserjs/ghacks-user.js/issues/180).

[crssi]

You mean to you have changed it to true? False will break OWA.

[ghost]

Yes, I mean I set it to true for OWA to work, but unfortunately MT still doesn't work.

[crssi]

First try with disabled firefox extensions, to be sure some extension does not create a mess.
If there is still a problem, then make a backup of your profile folder and continue with step 7 here https://github.com/ghacksuserjs/ghacks-user.js/wiki/1.4-Troubleshooting
When you find which setting is the cause, restore your profile from backup and change the setting in user.js to your desired value.
Let us know which one is the breakage cause for Microsoft Teams.

[crssi]

MS Team is lite version of SPPS (Share Point Portal Server) used for team collaboration.
Until @passboltUser finds out which setting is the breakage reason, it is maybe premature to jump into a conclusion. Maybe there is no user.js "problem" at all and might be some extension(s) itself or extension miss configuration that causes it.

[ghost]

@crssi Of course I'm not using any extensions (I linked to https://github.com/ghacksuserjs/ghacks-user.js/issues/180 and there I said that so I thought it goes without saying).

@Thorin-Oakenpants I'm not a fan of using browser for things it's not necessarily designed to. WebRTC is different from M$ Teams. What about IP leaks from WebRTC, still an issue?

Well, I guess I need to add the user.js settings half by half and test (sure, will let you know (that also goes without saying)).

[ghost]

Found it. It is user_pref("privacy.firstparty.isolate", true);. dom.indexedDB.enabled is required too BTW.

[crssi]

I don't believe any cross domain login is involved. Normally here everything goes over SSO.

[ghost]

@Thorin-Oakenpants Tried your suggestion and set privacy.firstparty.isolate.restrict_opener_access to false, and to true to test. Doesn't matter what I set, privacy.firstparty.isolate needs to be false.

I think indexedDB needs to be disabled (this rather big database keeps too much data).

Wouldn't be surprised if cross domain login is involved.

[ghost]

I also have only sometimes sites that need indexedDB, but those are also not my main sites, but are found randomly and I use the Iridium Browser for those rare instances so that that found site just works for the minute that I need it (Iridium Browser is not a replacement for the users.js settings because Iridum still has way too many bad settings which should be disabled like Canvas, WebRTC, ......).
Yes indeed, one I think nice way, if indexedDB is enabled, to control its data, would be to somehow delete its contents when Firefox is closed. Similar to cookies (I modded your users.js to i.e. delete my cookies when I close Firefox).