Well, Chrome just updated to 2.0.177.1 ...

Here are the changes:

Updates:
Update WebKit 530.8 (r42805)
Update V8 to version 1.2.0. (Issue: 10726)
Update to version 26 of open-vcdiff (underpinnings for SDCH decoder)

Visible Changes:
-Allow Flash (and other plugins) to be installed without restarting the browser. -This works by monitoring the MozillaPlugins registry key and reloading the plugin list afterwards. (Issue: 10574)
-On some sites text disappears or is never drawn. For example, on Google Calendar, the titles for all day events do not display. (Issue: 9904)
-Added "Restore closed tab" item to Tab menu.
-Fixes a bug where scrolling up would draw over the horizontal scrollbar on Mac.
-Fix issue: If SpellChecker is disabled through UI, then right-click context menu's spell checker language option should be unchecked. (Issue: 7239)
-Allow users to hit ctrl-shift-delete ("clear browsing data") even in fullscreen mode. (Issue: 9318)
-Fix a painting problem observed with windowless flash plugins, when they are initially created with a zero clip. (Issue: 10536)
-On uninstall ask whether to delete profile. (Issue: 8431)
-Disable the move/size/maximize entries on the system menu in fullscreen mode. (Issue: 8024)
-Add open/close animations to infobar, download shelf.
-Make sure radio buttons can't be toggled like checkboxes. (Issue: 10834)
-Disable RCtrl + RShift shortcut for changing directionality when no RTL language installed. (Issue: 9718)
-Fixes for selecting RTL text. (Issues: 6125, 8686)
-Fixes a problem where for some Indian locales, the automatic font fallback by Windows UI components leads to too tiny glyphs for UI strings. (Issue: 7319)

Crashes:
-Fix a crash where the ResourceMessageFilter is deleted before a SafeBrowsing check has completed. (Issue: 8544)
-Fix hang seen in plugin process. (Issue: 10711)
-Fix crash in setup.exe. (Issue: 10507)

-On some sites text disappears or is never drawn. For example, on Google Calendar, the titles for all day events do not display. (Issue: 9904)

This was bugging me.. mostly on twitter.

Still not 100% Acid3 compliant however.

Chrome keeps getting better.. at a fast pace !

Yeah, I also had text problems with Wordpress... now they're fixed!

@Kyrax

It scores 100/100 on the Acid3 test and is pixel per pixel equal to the reference.
So it is compliant except for the linktest failed error
But I have read somewhere that it is impossible to not have that error.

But I have been known to be wrong...

What is really bothering me is that it is not the webstandards.org own "Acid tests" that set the rules for the internet but it is still Internet Explorer 7