Chrome for Android. Finally.

In fact it detracts from the mail with a misleading title.

Honeycomb already does Chrome sync, logic would say that it'll show up in ICS on phones as well.

Well, Firefox Mobile does sync bookmarks & history. But I think most mobile devices are still limited enough you can't really run a full-featured browser and get good performance -- thus the current lack of a direct Chrome port on Android.[1]

Trying to 'sync' extensions between two radically different apps probably isn't worth the headaches it would cause... even an auto-suggest would probably mess up enough to be annoying.

[1] And, despite this article's headline, that doesn't seem to have been announced.

Yeah, it would be a huge win for security as well. Users will not be at the mercy of their hardware vendor to provide an n-1 OS update that may or may not address all security issues.

Also, as petegrif mentioned below if this means Android browser getting NaCl and extensions support - that would open up lot of new possibilities.

I hope that it means that the Android Browser starts rendering as well as Chrome on the Desktop. They are much more different browsers, at this point, than you'd expect. (Granted, my only experience has been the Android Browser on the Galaxy Tab we just purchased.) For instance, CSS transforms have artifacts, 3D CSS transforms aren't hardware accelerated, strange z-index and focus bugs, and more. I'd imagine more equivalence with desktop Chrome would straighten some of these out.

I'm trying to make sense of this myself, but it seems as if the seperate Android WebKit project is no longer necessary as there is enough code in common to justify a Chrome port to the Android platform (similar to Linux/Windows/Mac ports). This gives added benefits of layout rendering being more in sync with Chromium. I'm hoping it paves the way for more Chrome-browser features finding their way to Android browsers or even the default browser.

Android already supports SVG as of Honeycomb.