Monday, November 30, 2009

Dev Channel Update

The Dev channel has been updated to 4.0.249.21 for Linux.

All

Linux
  • [r32941] Change the default CSS fonts for Simplified Chinese, Japanese, Korean and Thai on Linux to poplular Linux fonts. (Issue: 20171)
  • [r33145] Properly detect KDE4 on newer systems (e.g. [K]Ubuntu 9.04). (Issue: 25938)

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.

Anthony Laforge
Google Chrome Program Manager

Tuesday, November 24, 2009

Google Chrome Frame Update

Google Chrome Frame has been updated to 4.0.255.0.

ChromeFrame
  • Empty user directories are properly deleted when Google Chrome Frame is un-installed. (Issue: 27483)
  • Crash fixes (Issues: 27414, 27695, 27662)
  • Ensure that the renderer has focus when ChromeFrame navigates to a URL in IE full tab mode. (Issue: 22745)


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.

Anthony Laforge
Google Chrome Program Manager

Dev Channel Update

The Dev channel has been updated to 4.0.249.12 for Mac.

Mac


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.

Anthony Laforge
Google Chrome Program Manager

Monday, November 23, 2009

Dev Channel Update

The Dev channel has been updated to 4.0.249.11 for Windows and Linux. This release includes relatively minor updates for both platforms.

Windows
  • Make the char encoding indicator visible again on Windows (Issue: 26438).
Extensions
  • Extension popups shrink when their contents shrink. (Issue: 26471)

    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.

    Anthony Laforge
    Google Chrome Program Manager

    Friday, November 20, 2009

    Dev Channel Update

    The Dev channel has been updated to 4.0.249.4 for all platforms (Windows, Mac, and Linux).

    All Platforms
    • Fixed - Issue 27897: [Extension] Some extensions crash after installing 4.0.249.0
    • Fixed - Issue 27900: [Extension] Reload on crash infobar causes more crashes
    Windows
    • Fixed top windows crasher. (Issues: 27856, 28096)
    • Fixed a crashing race condition in bookmark synchronization. (Issue: 23251)
    • Make the character encoding indicator visible again on Windows. (Issue: 26438)
    Mac
    Linux
    • Pasting some text into the Omnibox should no longer crash Google Chrome. (Issue: 27698)
    Extensions
    • Tab traversal in popups fixed on Windows, also a few other focus-related bugs. (Issues: 22654, 28086, 28087)
      Known Issues:
      • Issue 27902: [Extension] Extension link on new tab page doesn't work properly

      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 athttp://code.google.com/p/chromium/issues/entry.

      Anthony Laforge
      Google Chrome Program Manager

      Wednesday, November 18, 2009

      Google Chrome Frame Update: Bug Fixes

      Google Chrome Frame has been updated to version 4.0.245.1. All users should be updated automatically.


      This release fixes several of the most common crashes and the following issues:

      • Network requests fail randomly (Issue 27401).
      • Fix issues with CFInstall.js to better detect compatible OS and browser versions, allow users to cancel the installation frame, and not cache the isAvailable result (Issues 22738, 23057, and 23132).
      • Don't use Google Chrome Frame for frames or iframes (Issue 22989).
      • Follow redirects properly (Issue 25643).
      • IE8 freezing intermittently (Issue 24007).
      • Remove data directories on uninstall (Issue 27483).
      Security Fix
      Google Chrome Frame 4.0.223.9 and earlier versions were vulnerable to a cross-origin bypass.

      Severity: High. An attacker could have bypassed cross-origin protections. Although important, "High" severity issues do not permit persistent malware to infect a user's machine. We're unaware of any exploitation of this issue.

      Credit: Thanks to Billy Rios and Microsoft Vulnerability Research (MSVR) and also to Lostmon for finding and reporting this vulnerability responsibly.

      -- Mark Larson, Google Chrome Team


      Monday, November 16, 2009

      Dev Channel Update


      The Dev channel has been updated to 4.0.249.0 for all platforms (Windows, Mac, and Linux).

      All Platforms
      • [r31779] Introduced Timeline and Storage panels in Chrome's Developer Tools
      Windows
      • Covered by All Platforms and Extensions.
      Mac
      Linux
      • [r31793] Visual fixes to the popup blocker in chrome theme mode (Issue: 26155).
      • [r31984] Status bubble should move out of the way of the mouse (Issue: 18311)
      Extensions
      • [r32008] Mostly fixes black flashing that happens during popup resize. (Issue: 25459)
      • [r31996] Re-enable database storage for extensions. (Issue: 27216)
      • [r31844] Fix a crash in ExtensionMessageService when a source renderer closed. (Issue: 27554)
      • [r31840] Fix a crash in BrowserActionButton::OnImageLoaded. (Issue: 27167)
      • [r31826] Fix a crash in ExtensionsService::ReloadExtension (Issue: 27199)

      Known Issues:
      • Issue 27897: [Extension] Some extensions crash after installing 4.0.249.0
      • Issue 27900: [Extension] Reload on crash infobar causes more crashes
      • Issue 27902: [Extension] Extension link on new tab page doesn't work properly



        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.

        Anthony Laforge
        Google Chrome Program Manager

        Friday, November 13, 2009

        Dev Channel Update

        The Dev channel has been updated to 4.0.245.0 for all platforms (Windows, Mac, and Linux). In this release we are continuing our focus on feature polish, stability improvements, and extensions work.

        All Platforms
        • [r31412] Kiosk Mode implementation. (Issue: 23145 – doesn't work on OS X yet)
        Windows
        • Update covered by extensions and all platforms.
        Mac
        • [r31428], [r31429], [r31432], [r31462] Download shelf polish.
        • [r31156] Download shelf animates out (Issue: 25602)
        • [r31200] Bookmark All Tabs... works (Issue: 25099)
        • [r31227] Engooden SSL code – saving on google docs should no longer hang forever (Issue: 21268)
        • [r31369, r31197] More keyboard handling fixes (Issue: 25856, 26115)
        • [r31287] Send keypress() events for more keys – ctrl-1 now works in docs (Issue: 25249)
        • [r31316] New Tab button has "pressed" and "hover" states (Issue: 26205)
        • [r31330] "Paste and Match Style" now has shortcut cmd-opt-shift-v instead of cmd-shift-v (Issue: 25205)
        • [r31297] Mouse tracking now works correctly on full-window plugins (Issue: 25288)
        • [r31561] Transparent plugins now draw correctly (Issue: 25820)
        • [r31585] PDFs downloaded again instead of being opened by the QuickTime plugin (Issue: 26075)
        Linux
        Extensions
        • [r31157] Don't reload extensions management page to refresh after install/uninstall/disable (Issue: 26163)
        • [r31179] User scripts not installed depending on download settings (Issue: 26801)
        • [r31204] Implement alert(), prompt(), and confirm() for extensions (Issue: 12126)
        • [r31285] Installed extensions should not have the 'reload' option (Issue: 26901)
        • [r31335] Make inspector for background page stay open across reloads (Issue: 25287)
        • [r31365] Add an info bubble after extension installation (Issue: 21412)
        • [r31540] Added a confirmation on extension uninstallation. (Issue: 27162)

        Known Issues:
        • Crash when closing a browser window when page action extensions are installed on Linux. (Issue: 25558)
        • Crash when clicking on the "Reload" button on the extension crashed info bar (Issue: 27199).
        • WebDatabase has been temporarily disabled.

        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 athttp://code.google.com/p/chromium/issues/entry.


        Anthony Laforge

        Google Chrome Program Manager

        Thursday, November 12, 2009

        Stable Update: Fix Google Chrome not Starting

        Google Chrome's Stable channel has been updated to 3.0.195.33 to fix a potential issue that could cause Google Chrome to stop working and a security issue.

        This release removes a dependency on a Windows library (t2embed.dll) that is not required by Google Chrome. If that library is missing or the user does not have permission to read it, earlier versions of Google Chrome would fail silently.

        Security Fix:
        CVE-2009-2816 Custom headers incorrectly sent for CORS OPTIONS request

        A malicious web site operator could set custom HTTP headers on cross-origin OPTIONS requests.


        Severity: Low. The majority of users are unlikely to be impacted by this issue.
        Credit: Apple Security
        Mitigations:
        • A victim would need to visit a page under an attacker's control.
        • The OPTIONS attribute is not widely supported by servers.

        Mark Larson, Google Chrome Team

        Friday, November 6, 2009

        Dev Channel Update

        The Dev channel has been updated to 4.0.237.0 for all platforms (Windows, Mac, and Linux). The focus on this release has been feature polish, stability improvement, and extensions work.

        Mac
        • Significant bookmark bar improvements.
        Linux
        • [r29163, r29299] Audio playing improvements in video/audio tags. (Issues: 23974, 20945, 17703)
        • [r29261] Fix international keyboard handling (alt-gr, ctrl+f). (Issues: 10846, 2215, 21471)
        • [r29657] ~ now works in the Omnibox to expand to home directories. (Issue: 18200)
        • [r29857] Fix conflicts between accelerator keys and HTML DOM accesskeys. (Issue: 21624)
        • [r29903] Inactive pinned tabs on linux throb when the title changes. (Issue: 25308)
        • Text drawn over rounded corners (including buttons) is no longer blurry. This affected a variety of sites, including Google Calendar and Google Reader.
        • As an experiment, we've changed the way clicking in the omnibox works. Leave a comment on the bug if it bothers you.

        Extensions
        • Lots of work to polish and stabilize the browser and page action APIs:
          • [r29556] Add badge text color API. Also change color APIs from ARGB to RGBA (breaking change, sorry!) (Issues: 24635, 24644, 25215)
          • [r29152, r29785] Browser actions (buttons, popups) are now implemented. (Issue: 23882, 23897)
          • [r29997] Add support for tab-specific state to browser actions. Also, fix the bug where only the first call to setIcon() works. (Issues: 24669,24472)
          • [r30346] Constrain browser action popups to a min/max size. Also fix some glitches in popup sizing. (Issue 25214)
          • [r30499] Use a better signature for the new page actions API (chrome.pageAction.* instead of chrome.pageActions.*). This is technically a breaking change, but hopefully not too many people had gotten around to using the new API yet. (Issue 25833)
        • [r29665] Remove toolstrips on linux. They were causing lots of crashes and are going away soon anyway. (Issue 25106)
        • [r29911] Add chrome.extension.sendRequest() -- a simpler way to do content script messaging. (Issue 23865)
        • [r30341] Add new event chrome.tabs.onStatusChange. This makes the common case of wanting to know when tabs load much easier. (Issue 21729)
        • Other miscellaneous cleanup:
          • [r29498] Correctly handle reloading in the task manager (Issue 18693)
          • [r29555] Fix bug where content scripts did not always apply to first page load (Issue 11547)
          • [r29714, r29922, r29935, r30219] Various cleanup for the extension management page (Issues 12119, 25509, 25471)
          • [r30091] Improve install UI on mac (Issue 19654)
          • [r30312] Filter out hidden files when loading and packing extensions (Issue 23004)
          • [r30326] Copy chrome.extension.getTabContentses() to chrome.extension.getExtensionTabs(). Nobody liked the old name. (Issue 21433)
          • [r30384] Use the puzzle piece as the default extension icon. (Issue 25906)
          • [r30481] Hide the theme install bubble a little earlier. It was overlapping with the install dialog on linux. (Issue 26130)

        Known Issues:
        • [r26861] - Autocomplete/ select box values are not being correctly populated in Linux. As a work around you can use the up/down arrow keys to view the current selection.
        • [r26600] - Task bar icon in Windows does not update/ display correctly.

        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.

        Anthony Laforge
        Google Chrome Program Manager