The Dev channel has been updated to 5.0.366.0 for ChromeFrame.

  • Better integration with Internet Explorer’s popup blocker.
  • Fixes issues regarding switching to chrome frame with meta tag.
  • Fixes a number of crashes.
  • Fixes issues with URL referrer parsing
The Dev channel has been updated to 5.0.366.0 for ChromeFrame.

  • Better integration with Internet Explorer’s popup blocker.
  • Fixes issues regarding switching to chrome frame with meta tag.
  • Fixes a number of crashes.
  • Fixes issues with URL referrer parsing

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

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

This release fixes two issues:

  • Fix to prevent crashes with the LastPass extension (Issue 38857)
  • Add the option to disable 'Offer to translate pages that aren't in a language I read' in Options > Under the Hood

This release also addresses one minor security issue:


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

--Mark Larson, Google Chrome Team
Google Chrome 4.1.249.1045 has been released to the Stable channel on Windows.

This release fixes two issues:

  • Fix to prevent crashes with the LastPass extension (Issue 38857)
  • Add the option to disable 'Offer to translate pages that aren't in a language I read' in Options > Under the Hood

This release also addresses one minor security issue:


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

--Mark Larson, Google Chrome Team

The Google Chrome Dev channel has been updated to 5.0.360.4 for Windows and Mac and 5.0.360.5 for Linux.

This release includes:
  • An integrated Adobe Flash Player Plug-in. We're integrating Adobe Flash Player 10.1.51.95 (10.1 beta 3) with Google Chrome so that you don't have to install it or worry about keeping it up-to-date. See the blog post on the Chromium blog for more details.

    To use the bundled Flash Player plug-in, add --enable-internal-flash to your command line or shortcut for starting Google Chrome.

  • A basic plug-in manager. The about:plugins page now lets you disable any plug-in from loading on all web pages. See the Known Issues section: this doesn't work in all cases yet if you already have Adobe Flash Player for Windows Firefox, Safari, or Opera installed.
Known Issues:
  • On Windows, if you have Adobe Flash Player for Windows Firefox, Safari, or Opera installed, the Flash plug-in will still work in some cases even if you decline the license agreement (when using --enable-internal-flash) or disable the Flash plugin from about:plugins. We're working on it.
  • If you disable (or enable) a plugin on about:plugins, your change does not take effect until you restart Google Chrome.
  • There is no bundled Adobe Flash Player plug-in for 64-bit Linux.
--Anthony LaForge, Google Chrome Program Manager

Google Chrome 5.0.342.8 has been released to the Beta channel on Windows. 


There's not much to report because most of the features were released previously in Chrome 4.1. This release does have an option in the Under the Hood section to let you disable automatic translations. 
Google Chrome 5.0.342.8 has been released to the Beta channel on Windows. 


There's not much to report because most of the features were released previously in Chrome 4.1. This release does have an option in the Under the Hood section to let you disable automatic translations. 


Now that all Beta users are on the same revision, we can disclose the following security issues fixed in this release:

  • [36553Low Don’t store non-text fields in the local Web Data database. Credit to Florian Rienhardt, BSI.
  • [Linux only] [36770High Certificate checking error. Credit to Hironori Bono and Adam Langley of the Chromium development community.
To get on the Beta channel, you can download Google Chrome fromIf 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.360.0 for Windows, Mac, and Linux platforms



All
  • Tabbed bookmark manager (Issue 4890)

  • Several Translate improvements

  • Fixed several AutoFill features (Issues 38218, 38009, 38538, 38104, 38681)
  • The Dev channel has been updated to 5.0.360.0 for Windows, Mac, and Linux platforms



    All
  • Tabbed bookmark manager (Issue 4890)

  • Several Translate improvements

  • Fixed several AutoFill features (Issues 38218, 38009, 38538, 38104, 38681)

  • Fixed long timeout when navigating away from slow pages (Issue 11007)


  • Linux
  • Fixed menu popups for Xinerama users (Issue 14184)

  • Better crash dumping


  • Security
  • Updated libpng for CVE-2010-0205


  • Known Issues
  • Issue 39196 Bookmarks under the chevron are disabled (fixed but not in this release)

  • Issue 39104: REGRESSION: Native dialogs got extended - fixed on trunk.

  • Issue 37874: REGRESSION: Visual Defect / Gray Bar on Frame and Superbar on Windows 7 and Vista Aero

  • Issue 39340: [Extensions] Chrome crashes when dragging browser action not-incognito-enabled from normal window to incognito window

  • Issue 39360: [Extensions] Facebook for Google Chrome extensions doesn't work in incognito mode

  • Issue 39372: [Extensions] new tab extensions takes effect in incognito mode even without "Allow this extension to run in incognito" option checked.


  • More details about additional changes are available in the svnlog of all revisions.

    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

    Karen Grunberg 

    Google Chrome 

    Google Chrome 5.0.342.7 has been released to the Beta channel for Mac users (we released Linux yesterday). The highlights for Mac are basically the same, with the addition of Full Screen view working.
    Google Chrome 5.0.342.7 has been released to the Beta channel for Mac users (we released Linux yesterday). The highlights for Mac are basically the same, with the addition of Full Screen view working.


    We finally have automatic translation for all Beta users.


    Highlights:
    • Automatic translations and greater control over content for privacy. The Google Chrome 4.1 Beta announcement for Windows explains these features in more detail.
    • Full screen mode
    • Really, really reload. A normal reload causes the browser to check with the server before reusing its cached content.  The server can decide whether or not the browser should use its cached content.  A force reload causes the browser to ignore its cached content and ask the server for a fresh copy of the page. Use Shift+Reload to force a reload (the reload keyboard shortcut varies by platform).
    To get on the Beta channel, you can download Google Chrome from http://www.google.com/chrome?platform=mac.


    If you find issues, please let us know by filing a bug.


    --Mark Larson, Google Chrome Team 

    Google Chrome 5.0.342.7 has been released to the Beta channel for Linux.

    We’ll be releasing 342 to Mac and Windows soon, but we wanted to get the Linux update out as quickly as possible to fix an issue with Google SSL sites failing with ‘error 107 (net::ERR_SSL_PROTOCOL_ERROR)’ (issue 
    Google Chrome 5.0.342.7 has been released to the Beta channel for Linux.

    We’ll be releasing 342 to Mac and Windows soon, but we wanted to get the Linux update out as quickly as possible to fix an issue with Google SSL sites failing with ‘error 107 (net::ERR_SSL_PROTOCOL_ERROR)’ (issue 37722).

    Here are the highlights since the 307.11 update:
    • Automatic translations and greater control over content for privacy. The Google Chrome 4.1 Beta announcement for Windows explains these features in more detail.
    • Really, really reload. A normal reload causes the browser to check with the server before reusing its cached content.  The server can decide whether or not the browser should use its cached content.  A force reload causes the browser to ignore its cached content and ask the server for a fresh copy of the page. Use Shift+Reload to force a reload (the reload keyboard shortcut varies by platform).
    To get on the Beta channel, you can download Google Chrome from  http://www.google.com/chrome?platform=linux

    If you find issues, please let us know: http://code.google.com/p/chromium/issues/entry?template=Defect%20on%20Linux

    --Mark Larson, Google Chrome Team 

    Google Chrome 4.1.249.1042 has been released to the Windows Stable channel.


    This release fixes an issue with some extensions not installing from the Google Chrome extensions gallery (issue 38220).


    --Mark Larson, Google Chrome Team 
    Google Chrome 4.1.249.1042 has been released to the Windows Stable channel.


    This release fixes an issue with some extensions not installing from the Google Chrome extensions gallery (issue 38220).


    --Mark Larson, Google Chrome Team 

    Update: We've released 5.0.356.2 for Linux Dev channel users as well now.

    We have released Google Chrome 5.0.356.2 to the Dev channel on Windows and Mac to fix an issue where dragging anything with your mouse would freeze the tab. See issue 38414.
    Update: We've released 5.0.356.2 for Linux Dev channel users as well now.

    We have released Google Chrome 5.0.356.2 to the Dev channel on Windows and Mac to fix an issue where dragging anything with your mouse would freeze the tab. See issue 38414.

    --Mark Larson, Google Chrome Team

    The Dev channel has been updated to 5.0.356.0 for Mac.

    The Dev channel has been updated to 5.0.356.0 for Mac.

    Mac

    • [r41041] Implement Mac Address Book "me" card integration with Autofill. (Issue: 36496)
    • Various improvements to the bookmark folder menus.
    • [r40444] Fix beach ball/performance issues with the cookie manager. (Issue: 35134)
    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.356.0 for Windows, Linux, and Google Chrome Frame.

    All
    • Form autofill enabled by default for new profiles. (Issue: 37466)
    Windows
    The Dev channel has been updated to 5.0.356.0 for Windows, Linux, and Google Chrome Frame.

    All
    • Form autofill enabled by default for new profiles. (Issue: 37466)
    Windows

    Linux

    • [r40587] Client SSL Certificate Support (UI) for Linux. (Issue: 25241)
    • [r40795] Renderers can now figure out how much memory they're using and release it properly. (Issue: 32519)
    Chrome Frame
    • [r41754] Chrome frame should use "parentNode" instead of "parentElement" to get the DOM
    • [r41595] Better integration with host (InternetExplorer) popup blocker. (Issue: 34823)
    Known Issues
    • Cannot drag anything (text or images) in a content area. For example, dragging a thumbnail on the new tab page hangs the page. (Issues: 38414, 38556)
    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

    EDIT 23-Mar-10 (mal): Remove "[33572] Medium HTTP headers processed before SafeBrowsing check" from security issues fixed. This is not fixed in this release.

    The stable channel has been updated to 4.1.249.1036 for Windows, and includes the following features and security fixes (since 4.0):
    EDIT 23-Mar-10 (mal): Remove "[33572] Medium HTTP headers processed before SafeBrowsing check" from security issues fixed. This is not fixed in this release.

    The stable channel has been updated to 4.1.249.1036 for Windows, and includes the following features and security fixes (since 4.0):

    • Translate infobar.
    • Privacy features: content settings (cookies, images, JavaScript, plug-ins, pop-ups).
    • Disabling experimental new anti-reflected-XSS feature called "XSS Auditor". The feature is still experimental, and we're disabling it while we look into some serious performance issues in rare cases. Please see this post for more details about what the XSS Auditor is.

    Please see this feature announcment post for more info about translate and privacy.

    Security Fixes and rewards:
    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.

    Congratulations to Sergey Glazunov on receiving the first $1337 Chromium Security Reward for bug 35724.
    • [28804] [31880] High Race conditions and pointer errors in the sandbox infrastructure. Credit to Mark Dowd, under contract to Google Chrome Security Team.
    • [30801] [33445] Low Delete persisted metadata such as Web Databases and STS. Credit to Google Chrome Security Team (Chris Evans) and RSnake of ha.ckers.org.
    • [$500] [34978] High Memory error with malformed SVG. Credit to wushi of team509.
    • [$1337] [35724] High Integer overflows in WebKit JavaScript objects. Credit to Sergey Glazunov.
    • [36772] Medium HTTP basic auth dialog URL truncation.Credit to Google Chrome Security Team (Inferno).
    • [37007] Medium Bypass of download warning dialog. Credit to kuzzcc.
    • [$1000] [37383] High Cross-origin bypass. Credit to kuzzcc.
    • [$500] [Affected BETA only] [37061] High Memory error with empty SVG element. Credit to Aki Helin of OUSPG.

    List of all changes: http://build.chromium.org/buildbot/perf/dashboard/ui/changelog.html?url=/branches/249/src&range=38071:41527&mode=html


    - Orit Mazor, Google Chrome Team

    Google Chrome 5.0.342.5 has been released to the Dev channel on all platforms. This release has
    • A lot of improvements to the bookmark bar on the Mac.

      Note that there’s still an issue with folders with a lot of bookmarks. When you open the folder on the bookmarks bar, the list may extend below the bottom of the screen and you won’t be able to access the bookmarks at the bottom. A fix is coming soon. A workaround is to use the bookmark menu in the menu bar.

    • A lot of improvements to the quality of form Autofill.
    Google Chrome 5.0.342.5 has been released to the Dev channel on all platforms. This release has
    • A lot of improvements to the bookmark bar on the Mac.

      Note that there’s still an issue with folders with a lot of bookmarks. When you open the folder on the bookmarks bar, the list may extend below the bottom of the screen and you won’t be able to access the bookmarks at the bottom. A fix is coming soon. A workaround is to use the bookmark menu in the menu bar.

    • A lot of improvements to the quality of form Autofill.
    More details about additional changes are available in the svn log of all revisions.

    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.

    --Mark Larson, Google Chrome Team

    The Dev channel has been updated to 5.0.350.1 for Google Chrome Frame.

    • [r40547]
      Fix a crash in ChromeFrame which would occur if we clicked both mouse buttons on a link. (Issue: 37220)
    • [r40897]
      ChromeFrame now uses host provided popup blocker. (Issue: 34823)
    • [r41595] Better integration with host (InternetExplorer) popup blocker. (Issue: 34823)

    The Dev channel has been updated to 5.0.350.1 for Google Chrome Frame.

    • [r40547]
      Fix a crash in ChromeFrame which would occur if we clicked both mouse buttons on a link. (Issue: 37220)
    • [r40897]
      ChromeFrame now uses host provided popup blocker. (Issue: 34823)
    • [r41595] Better integration with host (InternetExplorer) popup blocker. (Issue: 34823)

    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 Google Chrome Beta channel for Windows has been updated to 4.1.249.1036. 


    Release highlights:

    • Translate infobar [UMA, 37734]

    More details about additional changes are available in the svn
    The Google Chrome Beta channel for Windows has been updated to 4.1.249.1036. 


    Release highlights:

    • Translate infobar [UMA, 37734]

    More details about additional changes are available in the svnlog of all revisions. 


    --Orit Mazor, Google Chrome Team




    • All:  Form auto-fill is not enabled by default (Issue 37466) - Fixed on Trunk
    • Windows: Browser crashes on quiting with Authentication dialog opened (Issue: 37698)  - Fixed on Trunk
    • Linux: Chromium Bookmark Sync Not Working (Issue: 36460)


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

    This release improves stability and fixes some known crashers (such as Issues: 370353767437567)

    Known Issues
    • All:  Form auto-fill is not enabled by default (Issue 37466) - Fixed on Trunk
    • Windows: Browser crashes on quiting with Authentication dialog opened (Issue: 37698)  - Fixed on Trunk
    • Linux: Chromium Bookmark Sync Not Working (Issue: 36460)
    More details about additional changes are available in the svn log of all revisions.

    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

    Karen Grunberg
    Google Chrome