Updates

• Oct. 28, 2021: The bug mentioned in the Sep. 22 update has been fixed.
• Sep. 22, 2021: There was a bug affecting Wayland Chrome/Chromium/Electron in the latest Sway/wlroots (i.e., the latest git commit). See https://github.com/swaywm/wlroots/issues/3168 and https://bugs.chromium.org/p/chromium/issues/detail?id=1246834. Before the bug was resolved, the workaround was to use the released versions of Sway/wlroots or just wait.

In the past, we may need to use XWayland when using Google Chrome or Chromium under the Wayland environment. But now (as of 01/04/2021), it’s possible to use native Wayland with Google Chrome/Chromium and even Electron-based apps if they are installed through the official repository or AUR. Just launch Google Chrome/Chromium with two additional flags:

1
$ google-chrome-stable --enable-features=UseOzonePlatform --ozone-platform=wayland

or

1
chromium --enable-features=UseOzonePlatform --ozone-platform=wayland

It’s the same for Electron-based apps:

1
<app executable> --enable-features=UseOzonePlatform --ozone-platform=wayland