I had the same issue with Teams a few years ago and I just switched to the browser version. Teams app was buggy anyway. No big deal.
The good thing with the browser version is rolling updates are immediate, no need to upgrade a flatpak or rpm. And if they fuck up, rollback is also immediate.
Also this is about removing the gnome x11 session package from the default install. That doesn't mean you can't run X11.
Having said that I don't know who would want to keep using X11 AND choose Fedora as its goto distro. This is a distro whose purpose is to push forward these kind of stuff, there are a number of much more conservative distros available and one could argue that if you are conservative and want to stay in the RPM/RH family you can use RHEL or a derivative distro such as Almalinux or Rocky. That is what I use on the media center computer in my living room for other reasons[1]. Back in the day someone would complain about outdated package but nowadays with tools like flatpak, podman and the toolbox this is just not true anymore.
[1] I don't power it up so often. I don't want to have tons of packages to update every time I power it up to watch a show on streaming. All I want is to be able to upgrade the browser's flatpak.
I use Slack in a Chrome tab and screen sharing works perfectly there. I don't know how they've managed to fuck their app up so much it just shows a black rectangle.
It's weird that it doesn't work since it uses webrtc for huddles. That's precisely what I had to enable in the browser to get various screen sharing websites to work.
Btw, this isn't for slack but teams: I use the website because their Linux app blows, but I actually use a totally different browser (chromium) to my main browser (firefox) intentionally. Occasionally when teams takes 100% cpu and memory for no reason, I can 'pkill chromium' without nuking firefox. So the "one less engine" argument wouldn't convince me.
Tabs are sharing the code though, because it comes from the same binary. Every electron app instead has its V8 and Blink in a separate binary that has to be loaded into its own RAM.
Why even install these web apps separately? You can even just create a shortcut for them that opens them in a separate browser window if you need that.
The good thing with the browser version is rolling updates are immediate, no need to upgrade a flatpak or rpm. And if they fuck up, rollback is also immediate.
Also this is about removing the gnome x11 session package from the default install. That doesn't mean you can't run X11.
Having said that I don't know who would want to keep using X11 AND choose Fedora as its goto distro. This is a distro whose purpose is to push forward these kind of stuff, there are a number of much more conservative distros available and one could argue that if you are conservative and want to stay in the RPM/RH family you can use RHEL or a derivative distro such as Almalinux or Rocky. That is what I use on the media center computer in my living room for other reasons[1]. Back in the day someone would complain about outdated package but nowadays with tools like flatpak, podman and the toolbox this is just not true anymore.
[1] I don't power it up so often. I don't want to have tons of packages to update every time I power it up to watch a show on streaming. All I want is to be able to upgrade the browser's flatpak.