[nicalsilva]

Firefox uses GTK to draw native-looking widgets. Basically, Gecko passes an X11 pixmap to GTK2 the latter draws the buttons/scroll bars/etc. into it with xrender. This means that Firefox either has to do all of the rendering with xrender and pixmaps, or do an expensive read-back of the native widgets from the pixmap and draw other web content into whatever kind of surface it wants. The thing is, we really really want to move away from xrender. GTK3 has a slightly different API for this and can draw native widgets into any kind of surface that can be wrapped in a cairo context. So for Firefox, the most important part of moving to GTK3 is the removal of this dependency to X11 and xrender. Chrome (as far as I know) doesn't do native-looking widgets (and to be honest I would be happier if Firefox didn't either), so moving to GTK3 is not that big of a deal for Chrome because it doesn't use the GTK nearly as much as Fireox does.

[adrusi]

I don't really use chrome. If the widgets don't look native that's fine, but do they behave natively? If they're not drawn by gtk, do the standard keybindings work if they've been changed from gtk's defaults. If not that would be quite infuriating to use.