Google Chrome - nine things we've found since launch

Google must be very happy with the coverage Chrome has gathered. But it's not all good news.

Google must be very happy with the coverage Chrome has gathered. But it's not all good news. Here are eight of the more interesting things to come out of the woodwork since the browser broke cover.

It's got bugs. No surprise there - but the good thing is we are welcome to read the buglist and follow their progress through the debugging cycle.

Whether you press enter or not, the auto-suggest feature will deliver all the keystrokes you put into the combined "Omnibox" URL/search field to Google, who'll store 2 percent of those – with the IP address of the user.

Chrome was built over two years and at least twenty developers, but combines elements from a whole host of small companies bought by Google and other outside sources.

Chrome is probably going onto Android, Google's mobile platform. To that end, key components such as V8 and WebKits are already available in ARM.

Is Chrome fastest? The argument rages – with Mozilla now claiming the SunSpider crown for TraceMonkey on FireFox 3.1.

Chrome's already had its first security flaw – a problem with the WebKit rendering engine. The problem has already been fixed in later versions of WebKit than the one the browser uses, so is in little danger of making it into the release.

According to Clicky's analysis of 45,000 websites, Chrome is now the world's fourth favourite browser, generating around three percent of monitored clicks.

V8, the engine behind Chrome's performance, was conceived in a Danish farmhouse.

Chrome requires an as-yet-unreleased update to Java, Java SE 6u10, to run Java code.


You have been successfully signed up. To sign up for more newsletters or to manage your account, visit the Newsletter Subscription Center.
See All
See All