Chrome 3.0 and 4.0 Updated on the Stable and Dev Channel

Article by George Norman (Cybersecurity Editor)

on 06 Nov 2009

The guys over at Google are keeping as busy, of not more so, as the guys over at Mozilla. While the Mozilla Foundation has recently released Firefox 3.6 Beta 1 and Firefox 3.5.5, Mountain View-based search engine giant Google has updated the Chrome browser on all the channels – the dev channel, the Beta channel, and the stable channel.

On the dev (short for developer) channel, Chrome has been updated to version 4.0.229.1. This is a Mac OS X only update that comes with the following highlights:
  • Show "Loading" bubble while loading a theme
  • Various keyboard handling fixes
  • Do not send some keyboard shortcuts to the renderers; e.g. cmd-w, cmd-t, ctrl-tab
  • "Copy image" now works
  • If auto-update happens, About box now says "update is available" and "restart needed for latest version"
  • Cmd-clicking back button now opens history page in new background tab
  • Form resubmission warning dialog implemented
  • Use Helvetica rather than Arial for several things

You can get on the Google Chrome dev channel here.

On the Beta channel, Chrome has been updated to version 4.0.223.16. This is the first chrome 4.0 release on the Beta channel. It comes with significant JavaScript improvements (30% faster than Chrome 3.0 stable) and bookmark sync .

You can get on the Google Chrome Beta channel here.

On the stable channel, Chrome has been updated to version 3.0.195.32. This is a stability and security update that addresses the following issues:
  • Resolved a history issue that affected going back from queries in Google Maps.
  • Fixed issue with Adobe Acrobat Reader 9.2, where no content would be displayed
  • Fixed an infinite loop in AAC decoding
  • Fixed a top crasher
  • Fix issues where setInterval sometimes eats 100% CPU
  • Fixed security issues where the user was not warned that some file types (like SVG, MHT and XML) can execute JavaScript
  • Fixed security issue where a malicious site could use the Gears SQL API to put SQL metadata into a bad state, which would lead to memory corruption

You can get Google Chrome 3.0 Stable here.


Latest News


Sony's 'Attack of the Blockbusters Sale' Slashes Prices in Half for a Ton of PS4 Games

17 Aug 2017

How Samsung's New T5 Compares to the Old T3 Portable SSD (Infographic)

17 Aug 2017

See all