Update on Oct 28, 2021: the bug mentioned in the update of Sep 22 has been fixed.
Update on Sep 22, 2021: there’s a bug affecting using 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 is resolved, either 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:
It’s the same for electron-based apps:
google chrome fast open with wayland, thank
Why you still have to fuck with additional parameters to run chrome in wayland ?
You probably don’t. The upstream’s roadmap was to make Ozone the default and discard these flags in the second half of 2021, which is now. I don’t know their progress because I don’t use Chrome now. No matter what, older electron-based apps still need these flags until the developers upgrade their Electron.
no, just change chrome://flags/#ozone-platform-hint to auto
Chrome Works well! You saved me much troubleshooting! Thanks!
Any luck sharing an application window into a Google Meet?
go to chrome://flags and search for wayland. there’ll be a setting “WebRTC PipeWire support”, put that on enabled and restart. Then you can share your application window or the entire screen via meet. Just make sure to select “Emtire Screen” option on the first prompt and then there’ll be a second prompt where you’ll be able to select the window to share.