However, enabling experimental native Wayland support with Ubuntu’s Chromium Snap is not possible, as that release forces Wayland support off.
Back in 2020, Ubuntu’s chromium-browser has been having a bug report about Chromium’s Wayland support being disabled by the “DISABLE_WAYLAND” option.
Discussion of this bug report restarted in March, and now with the latest Chromium snap build, new changes have landed, DISABLE_WAYLAND support is not set, thus forcing the Wayland support code in Ozone not to be built.
The Chromium browser snap on Ubuntu still defaults to X11/XWayland by default, but at least it now allows the option to use the native Wayland code path at runtime if needed.
Those running a Chromium Snap build in the past week who want to use the web browser’s native Wayland code can adjust your default preferences via chrome://flags/#ozon-platform-hint.
learn more:
