Chromium's Ozone Wayland Back-End Is Now Considered Beta, Aiming To Ship Next Year

[phoronix]

Phoronix: Chromium's Ozone Wayland Back-End Is Now Considered Beta, Aiming To Ship Next Year

For years there has been work on a Wayland back-end to Ozone, the Google component for abstracting user-interface elements and input/window handling among other tasks across platforms. It looks like in 2020 the Ozone Wayland support will be in good standing and promoted out of beta...

http://www.phoronix.com/scan.php?page=news_item&px=Ozone-Wayland-Next-Year

[cl333r]

I use both browsers but I'm switching to the first browser that supports Wayland 100% or hw accelerated video playback.

[boxie]

I use both browsers but I'm switching to the first browser that supports Wayland 100% or hw accelerated video playback.

I too use a plethora of chromium / firefox browsers and looking forward to both of these things working well out of the box.

sorta more excited for chromium because then all the electron based apps I use just magically become wayland apps too!

[Britoid]

I use both browsers but I'm switching to the first browser that supports Wayland 100% or hw accelerated video playback.

So Firefox or GNOME Web?

[carewolf]

Heh, QtWebEngine based on Chromium has been available on Wayland for years. But does that using Qt Ozone backend.

[latalante]

Heh, QtWebEngine based on Chromium has been available on Wayland for years. But does that using Qt Ozone backend.

Ozone can be built for at least five years.

Currently, this is no longer a separate fork, only a part of chromium.
https://bugs.chromium.org/p/chromium...tail?id=578890

He's still in trouble. Current Sway prevents chromium from starting (remove xdg-shell v6 support).
https://github.com/swaywm/sway/commi...b1d718bd84d4d0
https://bugs.chromium.org/p/chromium...tail?id=997631

Pkbuild for Archlinux.

https://aur.archlinux.org/packages/chromium-ozone/

Precompiled binaries for Fedora.
https://copr-be.cloud.fedoraproject....hromium-ozone/

[timrichardson]

So Firefox or GNOME Web?

Firefox can't do hardware video decoding. Something else that may happen in 2020, but more likely 2021 in my opinion. There is no sight of it.
It's easy to get video decoding in Chromium, most distributions have an easily available build. I've been using it for 12 months on Ubuntu. I have no idea if this Wayland back end will break this, but I think we'll be ok considering that hardware decoding works on ChromeOS (in proper Chrome) and that's not X.
So I bet Chrome/Chromium will beat Firefox to native Wayland + hardware decoding.

[xpris]

Firefox can't do hardware video decoding. Something else that may happen in 2020, but more likely 2021 in my opinion. There is no sight of it.
It's easy to get video decoding in Chromium, most distributions have an easily available build. I've been using it for 12 months on Ubuntu. I have no idea if this Wayland back end will break this, but I think we'll be ok considering that hardware decoding works on ChromeOS (in proper Chrome) and that's not X.
So I bet Chrome/Chromium will beat Firefox to native Wayland + hardware decoding.

Mozilla add hw video decoding for Linux in Servo engine few months ago. So If all goes well, we should see it soon in Firefox.

[royce]

Hopefully. I'm currently using a hack to send Youtube vids to mpv as otherwise watching anything kills my battery.

[carewolf]

Ozone can be built for at least five years.

Currently, this is no longer a separate fork, only a part of chromium.
https://bugs.chromium.org/p/chromium...tail?id=578890

Yes, but it is a different build of Chromium. You either build it for Ozone or for X11. You can theoretically use an Ozone X11 backend but it works poorly upstream.