According to what I've seen elsewhere Google moved very quickly to plug one of those holes - e.g. see http://googlechromereleases.blogspot.com/2012/03/chrome-stable-channel-update.html
Nice to know that the Chrome team are continuing to take security seriously.

crossy
According to what I've seen elsewhere Google moved very quickly to plug one of those holes - e.g. see http://googlechromereleases.blogspot.com/2012/03/chrome-stable-channel-update.html
Nice to know that the Chrome team are continuing to take security seriously.

Indeed, I remain a strong fan.

Rapid patching is great to see but you have to wonder whether this is regular practice or was rushed out because of the PR implications.

I've often been tempted by Chrome but haven't been able to shake the Opera habit yet (if you haven't seen their potato gun youtube video you should).

lkarunan
Rapid patching is great to see but you have to wonder whether this is regular practice or was rushed out because of the PR implications.

Looking at past practice (and I'm not sure Scribe will disagree) seems to show that the Chrome team are pretty much on the ball. As to the PR implications, there doesn't seem to have been much fanfare about the update, so I'd suspect that they're just wanting to “do it right”.

Certainly the Security Now! podcast folks (Leo Laporte and Steve Gibson) seem to like Chrome.