Google Chrome 4.1.249.1064 has been released to the Stable channel on Windows.

This release fixes the following issues:
  • Google Chrome was not using the correct path for the Java plugin for Java Version 6 Update 20.
  • 4.1.249.1059 was much slower on JavaScript benchmarks than 4.1.249.1045. (Issue 42158)

This release also fixes the following security issues:
Please see the Chromium security page for more detail. Note that the referenced bugs may be kept private until a majority of our users are up to date with the fix.
  • [$1000] [40445] High Cross-origin bypass in Google URL (GURL). Credit: Jordi Chancel.
  • [40487] High Memory corruption in HTML5 Media handling. Credit: David Bloom of Google Security Team.
  • [$500] [42294] High Memory corruption in font handling. Credit: wushi of team509.

If you find issues, please let us know: http://code.google.com/p/chromium/issues/entry

--Mark Larson, Google Chrome Team

Linux has been updated to 5.0.375.19

The Dev channel has been updated to 5.0.375.17 for Windows and Mac platforms.
Update: Windows, Mac, and Linux have been updated to 5.0.375.23, this was a crash fix release.
Update:
Linux has been updated to 5.0.375.19

The Dev channel has been updated to 5.0.375.17 for Windows and Mac platforms.

All
  • Disabled profile based Autofill (this will return in a future release)
  • Various UI features related to the url bar/ omnibox have been removed from this release (e.g. http:// truncation, star icon, etc...)


    • We are currently examining ways to address the usability issues that were raised and plan to reintroduce in the near future
  • Various crash fixes
Windows
  • We have restored the shortcuts for the bookmarks bar and bookmarks manager (Ctrl+B and Ctrl+Shift+B respectively)
Mac
  • See all
Known Issues
  • Drop down box does not close after clicking on the expand arrow a second time. (Issue: 42350)
  • [Linux] Autofill preference settings not being retained (Issue: 42446)
More details about additional changes are available in the svn log of all revision.

You can find out about getting on the Dev channel here: http://dev.chromium.org/getting-involved/dev-channel.

If you find new issues, please let us know by filing a bug at http://code.google.com/p/chromium/issues/entry

Anthony Laforge
Google Chrome


  • [$500] [39443High Type confusion error with forms. Credit: kuzzcc.
  • [39698High HTTP request error leading to possible XSRF. Credit: Meder Kydyraliev, Google Security Team
  • [40136Medium Local file reference through developer tools. Credit: Robert Swiecki, Google Security Team; Tavis Ormandy, Google Security Team.
  • [40137Medium Cross-site scripting in chrome://net-internals. Credit: Robert Swiecki, Google Security Team; Tavis Ormandy, Google Security Team.
  • [40138High Cross-site scripting in chrome://downloads. Credit: Robert Swiecki, Google Security Team; Tavis Ormandy, Google Security Team.
  • [40575Medium Pages might load with privileges of the New Tab page.
  • [$500] [40635High Memory corruption in V8 bindings. Credit: kuzzcc; Google Chrome Security Team (SkyLined); Michal Zalewski, Google Security Team.
Google Chrome 4.1.249.1059 has been released to the Stable channel on Windows.

This release fixes the following security issues:
Please see the Chromium security page for more detail. Note that the referenced bugs may be kept private until a majority of our users are up to date with the fix.
  • [$500] [39443High Type confusion error with forms. Credit: kuzzcc.
  • [39698High HTTP request error leading to possible XSRF. Credit: Meder Kydyraliev, Google Security Team
  • [40136Medium Local file reference through developer tools. Credit: Robert Swiecki, Google Security Team; Tavis Ormandy, Google Security Team.
  • [40137Medium Cross-site scripting in chrome://net-internals. Credit: Robert Swiecki, Google Security Team; Tavis Ormandy, Google Security Team.
  • [40138High Cross-site scripting in chrome://downloads. Credit: Robert Swiecki, Google Security Team; Tavis Ormandy, Google Security Team.
  • [40575Medium Pages might load with privileges of the New Tab page.
  • [$500] [40635High Memory corruption in V8 bindings. Credit: kuzzcc; Google Chrome Security Team (SkyLined); Michal Zalewski, Google Security Team.

If you find issues, please let us know: http://code.google.com/p/chromium/issues/entry

--Mark Larson, Google Chrome Team

The Dev channel has been updated to 5.0.375.3 for Windows

All
  • Flash enabled by default
  • Implement patterns for content setting exceptions.
  • A nicer looking video scaling algorithm is now used
Update: Linux, Mac, Windows have been updated to 5.0.375.9 to fix crashes.
Update: Linux and Chrome Frame have been released at 5.0.375.3, Mac has been released at 5.0.375.6

The Dev channel has been updated to 5.0.375.3 for Windows

All
  • Flash enabled by default
  • Implement patterns for content setting exceptions.
  • A nicer looking video scaling algorithm is now used
Windows
  • See All
More details about additional changes are available in the svn log of all revision.

You can find out about getting on the Dev channel here: http://dev.chromium.org/getting-involved/dev-channel.

If you find new issues, please let us know by filing a bug at http://code.google.com/p/chromium/issues/entry

Anthony Laforge
Google Chrome

The Dev channel has been updated to 5.0.371.0 for Windows, Mac, and Linux

All

  • Geolocation support (Issue 11246 and many others)
  • Fixed bug where HTML5 audio/video elements stopped firing timeupdate events (Issue 25185)
  • WebGL is running inside the sandbox under the --enable-webgl flag (i.e. this no longer requires the --no-sandbox flag to run). Browsing with the --no-sandbox is dangerous and we strongly recommend that you not do it.
  • Changes to the Omnibox (e.g. the bookmark star has moved, icon changes, etc...)

The Dev channel has been updated to 5.0.371.0 for Windows, Mac, and Linux

All

  • Geolocation support (Issue 11246 and many others)
  • Fixed bug where HTML5 audio/video elements stopped firing timeupdate events (Issue 25185)
  • WebGL is running inside the sandbox under the --enable-webgl flag (i.e. this no longer requires the --no-sandbox flag to run). Browsing with the --no-sandbox is dangerous and we strongly recommend that you not do it.
  • Changes to the Omnibox (e.g. the bookmark star has moved, icon changes, etc...)

Windows

  • See All

Mac

  • More omnibox reshuffling work-in-progress (Issue: 37865)

Linux

Known Issues

  • [Linux] HTML5 audio/video elements are not firing the ended event
  • [Linux] Right clicking "Copy Image" causes a crashe (Issue: 40448)

More details about additional changes are available in the svn log of all revision.

WebKit has been updated from r56820 to r57160.

You can find out about getting on the Dev channel here: http://dev.chromium.org/getting-involved/dev-channel.


If you find new issues, please let us know by filing a bug at http://code.google.com/p/chromium/issues/entry

Anthony Laforge
Google Chrome

Google Chrome 5.0.342.9 has been released to the Beta channel on all platforms. This update fixes issue 38220: some extensions cannot be installed.


--Mark Larson, Google Chrome Team
Google Chrome 5.0.342.9 has been released to the Beta channel on all platforms. This update fixes issue 38220: some extensions cannot be installed.


--Mark Larson, Google Chrome Team

The Dev channel has been updated to 5.0.366.2 for Windows and Linux, and 5.0.366.0 for Mac.
The Dev channel has been updated to 5.0.366.2 for Windows and Linux, and 5.0.366.0 for Mac.

All
  • [r42843] Fixed a bug with incognito extensions like RSS Subscription. (Issue: 39351)
  • [r42400] Will no longer automatically offer to translate in incognito mode. (Issue: 38107)
  • [r42981] Fix file upload code to not hang the HTTP session when the file is unreadable. (Issue: 30850)
Windows
  • See all
Mac
  • [r42411] Improvements to the bookmark manager (Issue: 39085)
  • [r42548] Re-enable pinned tabs; add support for mini and app tabs. (Issue: 36798)
  • [r43157] Fix selection issues with the cookie manager after deleting cookies. (Issue: 33320)
Linux
  • Some minor UI changes in the omnibox.
  • Recent regressions in font rendering have been fixed.
Known Issues
  • The location bar is undergoing renovation. Please excuse our dust.
  • The bookmark bar is not visible on the New Tab Page, will be fixed in next dev channel. Temporary workaround to bring it back is to enable it with a keyboard shortcut "Ctrl+B".
Important Notes
WebGL support in Chrome now runs inside the security sandbox. If you
have been testing WebGL, please remove the --no-sandbox flag from your
Chrome options. WebGL may be enabled via the --enable-webgl command
line option.

More details about additional changes are available in the svn log of all revision.

You can find out about getting on the Dev channel here: http://dev.chromium.org/getting-involved/dev-channel.

If you find new issues, please let us know by filing a bug at http://code.google.com/p/chromium/issues/entry

Anthony Laforge
Google Chrome