Google today added support for extensions and bookmark synchronization to the production version of Chrome for Windows.
The new release also patched 13 security vulnerabilities in the browser, six of which Google ranked as "high" in its threat scoring system.
Although a beta of Chrome in December 2009 included support for both extensions and bookmark sync, this is the first time that the features have appeared in the "stable" build channel, a term Google uses in place of "final." Google also touted the growth of its extension gallery, which now has more than 1,500 add-ons, a five-fold increase over the 300 available at its debut last month.
Only Windows' stable edition supports extensions and sync; Linux users must use the beta channel build for the same features, while Mac owners have to drop all the way down into the least reliable version, dubbed the "developer" build by Google, to access extensions.
Chrome 220.127.116.11 patches a baker's dozen security vulnerabilities, including six tagged as a "high" threat. Details on four of the six serious flaws have been blocked on Chrome's bug tracker to prevent hackers from using the information to create exploits. "The...bugs may be kept private until a majority of our users are up to date with the fix," explained Anthony Laforge, a Chrome program manager, in a blog post today.
Google also used the opportunity to brag about Chrome's speed increase since the last stable build for Windows. "We've improved performance (as measured by Mozilla's Dromaeo DOM Core Tests) by 42% over our last stable release and 400% since our first stable release last year," claimed Nick Baum, yet another product manager, on the official Chrome blog today.
Chrome is now the third-most-used browser on the planet, having grabbed the No. 3 spot from Safari last month, according to Web measurement company NetApplications.com.
Gregg Keizer covers Microsoft, security issues, Apple, Web browsers and general technology breaking news for Computerworld. Follow Gregg on Twitter at @gkeizer, send e-mail to firstname.lastname@example.org or subscribe to Gregg's RSS feed .