Comment by aorth

19 hours ago

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.

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?

  • Works for me, using Fedora with Plasma. Just fire it up in Brave, and install it as a PWA.

    The one thing that bothers me is it can't tell if I'm at my machine when I'm not actively using it. People keep thinging I've bugered off from my desk.

  • 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.

Would be great if it was also possible to have it open the Team URIs in that App Mode instance instead of the browser itself — I assume it does not.

  • What kind of URLs does it use? If it's anything with a unique prefix (like Telegram's tg://), you can add it to the desktop file:

      MimeType=x-scheme-handler/foobar;
    

    and run `update-mime-database`.

    If not, I would write a shell wrapper and set it as the default browser; something to the effect of:

      #!/usr/bin/bash
      set -eu
      for arg in "$@"; do
        if [[ $arg == *whatever-url-teams-uses.com* ]]; then
          exec gtk-launch teams "$@"
        fi
      done
      exec gtk-launch firefox "$@"
    

    (gtk-launch uses flags from the .desktop file so you don't have to repeat them)