[fluffything]

I use the chromium ozone packages from the AUR with sway on Wayland and they work fine.

The real problem with wayland are all the apps that just don't support it. From emacs, to, e.g., all the electron apps built with older versions of chromium, etc. You can use them seamlessly with Xwayland, but then a lot of things work "weirdly", e.g., HiDPI displays blurry Xwayland apps, applications like obs-studio cannot record some apps, etc.

The the Sway ecosystem main drawbacks are the immaturity of the tools (e.g., waybar (i3bar replacement), wofi (rofi replacement), etc.) and the drawbacks of wlroots (e.g. lack of nvidia support in contrast to gnome and kde, etc.).

Many things kind of "just work" under Wayland, but many things also kind of just don't properly work. Using pipewire to, e.g., stream desktop apps via webchat from firefox/chrome works weirdly, streaming one monitor or one sway workspace from firefox/chrome does not work, capturing one workspace from sway using obs studio in another workspace does not work, etc.

[danshick]

WebRTC (firefox and chrome) can (usually) stream individual XWayland windows using the same mechanism that was in place for window sharing under X. Wayland native apps are not shareable (and may not be if/until some protocol changes are introduced).

I hope that fullscreen desktop sharing "just works" now that we've released xdg-desktop-portal-wlr[0]. If you have any trouble with it, hit me up on freenode #sway or raise an issue on this project. We're happy to help and looking for a broader user base to help us test it out.

[0] https://github.com/emersion/xdg-desktop-portal-wlr