zlacker

>>basemi+(OP)
The official client is absolutely terrible. But, I've found a much better solution: I tell all my customers Microsoft Teams doesn't work for us and they'll have to pick something else.

Kudos for at least trying to address this, MS should hang their head in shame, this is not the hardest problem to solve these days. If we could do it in 1995 they should be able to do it 30 years later.

>>jacque+G6x
The web-based one works perfectly on Linux. If anything it's better than the native Windows app.

Office 365 actually works better in Firefox in Linux than any other browser in Windows. It's like they've kind of given up on the whole OS thing, and have just decided to go with Linux.

>>Errone+2ex
True! I've been doing this for years on Linux. I use a dedicated Chromium instance in app mode:

  /usr/bin/chromium --ozone-platform=wayland --enable-features=UseOzonePlatform,WaylandWindowDecorations,WebRTCPipeWireCapturer --user-data-dir=/home/myuser/.config/chromium-ilri --app=https://teams.microsoft.com

Works incredibly well (put this in a `.desktop` file with `Exec=` and you can launch it via your desktop's launcher). Some of the settings may not be needed anymore, as Chromium has come a long way in terms of Wayland support. I use Firefox for everything else, but haven't tried Teams there.

>>aorth+Yfx
The only thing that does not work for me with Teams as chromium 'app' is the screen sharing (on Wayland). Does your --enable-features fix this?

>>snicke+dBx
Screen sharing from the browser usually works for me, but if ever it doesn't, as a workaround you can use OBS with a virtual webcam to share windows and screens as an overlay to the webcam stream. It's very easy.