aura+wayland shoud be an excellent improvement.
File a bug asking them to enable it on Linux when the kernel, libva, and other dependencies are up-to-date. If lots of bugs are opened about the deficiencies on Linux, they might reconsider whether crippling it by disabling hardware acceleration is actually reducing the number of bug reports.
Regardless, Google is only replacing GTK in the browser part of their browser, not the html engine, which doesn't directly connect with any toolkit. So just looking at the shell/UI alone, that is 100% written by google.
- Mesa compiled with VDPAU support. That means: if you use Ubuntu, you need at least a recompile.
- VDPAU libraries.
- Mesa 10.1. You need GLSL 1.50 for some HW decoding paths.
- vdpauinfo. Check if your VDPAU setup is working.
- The following in your ~/.bashrc file
Apart from that, you need the very latest Google Chrome Unstable build.Code:export LIBVA_DRIVER_NAME=vdpau export VDPAU_DRIVER=r600
Well, I definitely noticed how the initial website rendering after loading is a lot smoother for at least some websites, like e.g. google plus or youtube.
edit: but font rendering is looking very different. Not sure if it's better or worse yet. At least they don't have colored anti aliasing by default! Yay!
FYI, there are also builds for chromium from google, not just for chrome. Shamelessly copied from an AUR package:
Despite it being called chrome-linux.zip it is actually chromium. But of course it is still a binary from an american company, so if you're paranoid, rather compile it yourself.Code:wget http://commondatastorage.googleapis.com/chromium-browser-snapshots/Linux_x64/$(curl -s "http://commondatastorage.googleapis.com/chromium-browser-snapshots/Linux_x64/LAST_CHANGE")/chrome-linux.zip
The difference between chromium and chrome: If there is tracking or phone-home code in chromium enabled, it's a bug that's getting fixed. In chrome it's a feature.