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.

I'd be really happy if they get Android browser to support SVG.