@colemickens I realized chromium now (accidentially?) doesn't allow disabling ozone support - is that intended? See c7a503b.

Also note #72932 was merged, so updating the chromium binaries should be way less cumbersome.

@flokli Yes, I figured there would be some issues with complications with chromium here. IMO we should make life easy for ourselves, remove useOzone and always build with libxkbcommon/wayland but maybe a more granular solution is warranted?

LMK what you think, I might spend some time this weekend trying builds of chromium on a big VM somewhere.

If it makes sense, maybe the version bump, google-chrome, and chromium fixes should come together.

I'd say it depends on upstream - if there's a somewhat (still) supported way to build chromoum without ozone, we could put it behind the useOzone flag (but invert the default to match upstream). If that's currently not supported. I'd be fine with just removing the option entirely, and always building with libxkbcommon/wayland.

@colemickens thanks!

@flokli Ozone support for Chromium M87 is in e249bac (I've been waiting for this finally becoming the default for a long time...)

BTW, I finally figured out that I was testing this wrong, it looks like you need to do this:
google-chrome-unstable --enable-features=UseOzonePlatform --ozone-platform=wayland. aaaand it doesn't work for me. (note, I bumped chromium's upstream-info locally)

@colemickens I also couldn't get it to work properly :o

But I just tested this again with a667bc7 (since M87 is now in the beta channel) and on my test system it does work now 🎉; at least once per boot (don't ask me why... I didn't look into it but from the printed messages it might somehow mess up some internal state of the kernel driver?).
I tested google-chrome-beta under Sway with xwayland disable. It still prints a lot of error messages due to the lack of X11 and according to chrome://gpu/ it was falling back to software rendering (though it didn't feel any slower; but then again I don't remember ever testing software rendering on that machine) but the browsing experience seemed pretty normal from a quick test (a web GL demo did work and I could even watch 4K YT videos).