The Dev channel has been updated to 16.0.912.0 for Windows, Mac, Linux, and Chrome Frame.All

Updated V8 - 3.6.6.3

Native Client and Pepper plug-ins will be able to go use First Person controls for games and other applications after they go full screen and lock the mouse cursor. See PPB_MouseLock::LockMouse.

Mac

Chrome now offers improved battery life on Mac laptops with dual (integrated and discrete) GPUs. Currently the improvement is present on 2011 MacBook Pros running OS X 10.7.1, but will take effect on more machines as OS software updates are released.

Known Issues

Printing does not work - crashes the tab.

Crash in Instant (Issue 100521). Fixed on trunk; workaround is to disable Instant (if it’s already disabled and still crashes, please re-enable and disable, using the checkbox in Preferences -> Basics).

Full details about what changes are in this build are available in the SVN revision log. Interested in switching to the Beta or Stable channels? Find out how. If you find a new issue, please let us know byfiling a bug.Dharani GovindanGoogle Chrome

20 comments
:

Hoping to see the "Chrome now offers improved battery life on Mac laptops with dual (integrated and discrete) GPUs. Currently the improvement is present on 2011 MacBook Pros running OS X 10.7.1, but will take effect on more machines as OS software updates are released." soon on the older version of mac running 10.6.8..

At least on Facebook and this blog, the links seem a little messed. I mean, they seem ignoring the CSS "color" attribute and some other stuff. Linked images seem to add a border too, etc.Finally Twitter is usable again, and no more foobar text! Good job.

Ok, regarding my comment about "messed links", they are messed when they are invalid. For example, when we have DIV tags inside A tags, then CSS seems to be ignored. The header of this blog and Facebook have this example I said.

Yes, Twitter and font problems are gone... however they are nowhere to be seen on the SVN commit log (searching for border, radius, cleartype, font, antialiasing, smoothing, etc.), plus chromium issues on google code are still open (e.g.: http://code.google.com/p/chromium/issues/detail?id=97716 ).

I wonder what's going on, this looks like a regression to me, more than a fix