If you feel bored or adventurous, or both, or would just like to try the new Aura UI of Chromium (which will become default at some point), I encourage you to enable USE="aura" for www-client/chromium. Upstream still keeps it disabled by default, and that includes Google Chrome. In Gentoo it's easy to make a choice about this.
Aura is a new UI architecture which is GPU accelerated. You can read about the technical details in its documentation. Especially because of the use of hardware acceleration it'd be useful to get many people to test it. If these changes break in your configuration, you can know now (while it's still early in development process), report a bug (consider posting the bug link in the comments so I can ensure it gets proper attention), and get back to the working configuration.
Possible workaround for GPU problems is using --disable-gpu command-line flag. Note that this still means there is a bug that is unlikely to get fixed if you don't report it. It's also useful to include contents of about:gpu page in your bug report.
Finally, see the screenshots below for an idea how it looks like (click thumbnails to see original images):
with aura |
without aura |
5 comments:
i have 11" netbook and spacing in menu is waste of space for me... simple menu shouldn't teka whole hight of screen.
Thanks for adding it. Builds and runs fine, just one thing: The menus don't have a border (like in your screenshot) here so they look quite weird on a white background. Dunno if that's worth a bug report or caused by the window manager.
Here's a minor regression for you.
https://code.google.com/p/chromium/issues/detail?id=326033
Still the same problem of blank menus with this version: https://code.google.com/p/chromium/issues/detail?id=318285
I don't know whether this is reproducible on every system or whether it depends on the used window manager.
@michal - feel free to report a bug about this
@Alex - sounds like a bug, please file one (make sure to include the details, i.e. screenshot, window manager, gtk theme and anything else you think may be relevant). I'd recommend you to post the link to the bug here (or send to me directly if you prefer) so that it can get assigned proper labels more quickly.
@Michael - thanks
@Julien - thanks, note that the bug currently needs feedback - developers can't reproduce
Post a Comment