> Which version of Chrome broke the rounded corners?
They had rendering problems with several successive versions, as the "bug fixes" didn't for a while.
> What's its current market penetration?
That's not the point. They had a serious regression, which was pushed out to all Chrome users automatically because of their update policy. That one was cosmetic, but things like H.264 are breaking changes that remove whole chunks of functionality. The details don't really matter; the danger inherent in their process is the more serious problem.
> IE6 could learn from this.
Your example is somewhat ironic.
For one thing, IE6 is the bane of web developers everywhere because it didn't follow web standards -- not least because a lot of them hadn't been written yet. Sound familiar at all?
For another, IE6 is still used in a significant number of large organisations even today because those organisations value a stable, controllable platform as a foundation for their in-house developments more than they value the latest bells and whistles on the public web. Again, there's a lesson there for Chrome, Firefox, et al.
IE6 is still used in a significant number of large organisations because those large organisations have chosen to use implementations of fat expensive enterprise applications that have been customised sufficently to screw any chances of following the upgrade path for said fat expensive enterprise applications, meaning they'll only ever work properly in IE6.
At least that's the case where I work. Sigh.
> They had rendering problems with several successive versions, as the "bug fixes" didn't for a while.
Not so different than IE, right? It's really a speed of release issue, if I'm understanding you.
Well, it's a double-edged sword. Speedy releases mean speedy regressions and speedy bugfixes. Slow releases are the opposite.
> That's not the point
For me it is... but I think that ties in, below.
> significant number of large organisations even today because those organisations value a stable, controllable platform as a foundation for their in-house developments more than they value the latest bells and whistles on the public web.
We're definitely talking about some different markets here. The markets I work in simply don't target IE6 any longer. The baseline, if it includes IE at all--sometimes it's targeted at HTML-only specifically, is IE8 and whatever you can force IE7 to do.
When is IE6 going to cease to be the baseline in these other organizations? It's like its having a COBOL moment.
They had rendering problems with several successive versions, as the "bug fixes" didn't for a while.
> What's its current market penetration?
That's not the point. They had a serious regression, which was pushed out to all Chrome users automatically because of their update policy. That one was cosmetic, but things like H.264 are breaking changes that remove whole chunks of functionality. The details don't really matter; the danger inherent in their process is the more serious problem.
> IE6 could learn from this.
Your example is somewhat ironic.
For one thing, IE6 is the bane of web developers everywhere because it didn't follow web standards -- not least because a lot of them hadn't been written yet. Sound familiar at all?
For another, IE6 is still used in a significant number of large organisations even today because those organisations value a stable, controllable platform as a foundation for their in-house developments more than they value the latest bells and whistles on the public web. Again, there's a lesson there for Chrome, Firefox, et al.