For those who use the chromium web browser on Ubuntu through the snap package, the latest build now has (optional) Wayland support enabled. For a long time, X11 and Wayland ozone support exist in the form of various test programs.
However, it is impossible to enable experimental local Wayland support with Ubuntu's Chromium snap, because Wayland support is forcibly turned off in this version.
Back in 2020, Ubuntu Chrome browser had an error report that Chrome's Wayland support was disabled by the "disable _wayland" option.
The discussion of this bug report was restarted in March. Now, with the latest chromium snap construction, new changes have been implemented and disabled_ Wayland support is not set, which forces Wayland support code in ozone not to be built.
By default, the Chrome browser snap on Ubuntu still defaults to X11 / xwayland, but at least it now allows you to choose to use the local Wayland code path at runtime if necessary.
For those users who have run the chrome snap build in the past week, if they want to use the local Wayland code of the web browser, they can chrome://flags/#ozon -Platform hint adjust your default preferences.
Learn more: