Chromium Browser Is Running Great On Wayland

[phoronix]

Phoronix: Chromium Browser Is Running Great On Wayland

For several months now Intel developers have been working on a new Ozone-Wayland project that allows Google's Chrome/Chromium browsers and other applications to work on Wayland. Google's Ozone component provides the windowing system / input abstraction layer that is where this implementation for Wayland is being plugged into. After much investment, the Chromium browser is now starting to run great with Wayland...

http://www.phoronix.com/vr.php?view=MTU5NTU

[mrugiero]

I wonder:
- Isn't the Chromium window lacking borders? Or it is just my memory failing/an interface change? I haven't used Chromium in more than a year, so maybe I just forgot how it looked (also, I usually maximize my browser), but I believe I remember it having thicker borders.
- Why is it running without the sandbox?

[newwen]

I wonder:
- Isn't the Chromium window lacking borders? Or it is just my memory failing/an interface change? I haven't used Chromium in more than a year, so maybe I just forgot how it looked (also, I usually maximize my browser), but I believe I remember it having thicker borders.
- Why is it running without the sandbox?

I've noticed that too. In ubuntu (X.org) it is using window borders, but under wayland they're using client side decorations with no borders, which looks much better in my opinion.

[dalingrin]

I hope this will finally allow for per pixel scrolling like Windows and Mac.

[kaprikawn]

Why is Intel doing this, what's in it for them? It's great and all, but I'm just wondering.

Also, is there any advantages to ChromeOS with this? Does Wayland use more or fewer resources to draw to the screen than whatever ChromeOS currently uses?

[paintbynumbers]

Why is Intel doing this, what's in it for them? It's great and all, but I'm just wondering.

Also, is there any advantages to ChromeOS with this? Does Wayland use more or fewer resources to draw to the screen than whatever ChromeOS currently uses?

I believe Google may be using X as the ChromeOS display server today and Intel already has a vested interest in Wayland replacing X (they pay many of the developers). It would be good for them to get some large players in the industry to switch to Wayland.

May the more important fact is that the web browser is arguably one of the most important on a machine today. Firefox has yet to finish their port to GTK3 to allow them to run natively on Wayland.

[sarmad]

I hope this will finally allow for per pixel scrolling like Windows and Mac.

Why would they need Wayland for per-pixel scrolling? Firefox seems to be doing it on xorg.

[dalingrin]

Why would they need Wayland for per-pixel scrolling? Firefox seems to be doing it on xorg.

AFAIK firefox does not do per-pixel scrolling in Linux. Firefox only gets scroll wheel events which by default scrolls 3 lines per increment. Firefox does use an animation to smooth the transition of 3 lines but its not nearly as nice as per-pixel scrolling. Wayland is not required for per-pixel scrolling but the older toolkits like GTK2 do not support it. I'm hoping the clean slate of Wayland + Aura would get per pixel scrolling in Chromium.

[uid313]

Performance

But Wayland have less performance than X.org Server, right?

[kaprikawn]

But Wayland have less performance than X.org Server, right?

X.org has been around since the late 70s, it's fairly mature software. Wayland is up-and-coming. Stop trolling idiot.