From the issue tracker:

> In UI review we decided that these scrollbars are OK for an M32 release, and that if there's bad user uproar we can live with it for one milestone then change in M33.

I wonder how pervasive this view is within the Chrome team. It actually explains a lot of issues I have run into that suddenly get fixed in the next release. I thought they were just bugs that had slipped by, but now am wondering how many were by design.

It's really horrible, here's the same radio group in Firefox and new Chrome:

Firefox: http://i.imgur.com/T8dWHcl.png

Chrome: http://i.imgur.com/EMNjV4P.png

The Chrome one somehow removes padding and also looks like a disabled control when in fact it isn't.

Chrome's renderer has always been extraordinarily ugly coming from Firefox. HTML Forms and font rendering specifically.

Can anyone explain the use case for the arrows as opposed to using keyboard arrows?

Removing them seems like a great step, but I might be brainwashed by the fact that Mac OS has done away with them already.

I don't care much for the arrows. The main issue for me is the lack of consistency with other native Windows applications, and that this also affects other widgets such as check boxes, radio buttons and drop down menus, which now feature a horrible fade animation.

That definitely makes sense. This isn't a case for saying it's "OK," but I feel that a browser is its own sort of contained environment, or at least people have come to accept it as that (since we have applications within each browser) and there is generally not much consistency with native UI elements at that level, so it's mainly that this consistency has been slowly degraded over time and people seem used to it not being consistent enough so that it's OK for the browser to make its own rules to some extent.

They already don't use native tabs (which most OS interfaces provide) and I'd call this a positive. In fact, I'd argue that many of the native UI elements are customized, but most people are used to that, largely because the customizations improve the product, so that's kind of why I asked the original question: what about this change makes the product worse in practice, why not insist all elements be native then if it's just an argument for consistency and not one for a loss of usability/productivity?

I am surprised at the number of people using the scrollbar arrows.

The new scrollbars are annoyingly thin and hard to see, though.

I'm surprised this doesn't interfere with accessibility guidelines.

Chrome's scrollbar changes or the non-native Aura UI itself?

Both sets of changes, but in particular, the scrollbar changes.

Was about to say but didnt want to hijack the topic. Also there is plenty of problems with low-level graphics cards rendering links and bold text. It looks very blurry now.