Google Chrome Releases: Dev Release: 0.4.154.18

Google Chrome 0.4.154.18 has been released to the Dev channel ONLY. This release introduces a couple of new features (and, as always, fixes a few bugs).

About the Dev Channel
The Dev channel lets you test the latest fixes and get access to new features as they're being developed. You can learn more about the Dev channel and how to subscribe here:http://dev.chromium.org/getting-involved/dev-channel/.


Reminder: please file (or update existing) issues at http://code.google.com/p/chromium/issues.

New Features

• Bookmark manager with import/export.
  Use the 'Customize and control Google Chrome' (wrench) menu to open the Bookmark manager. You can search bookmarks, create folders, and drag and drop bookmarks to new locations. The Bookmark Manager's Tools menu lets you export or import bookmarks.
  
  
• Privacy section in Options.
  We grouped together all of the configuration options for features that might send data to another service. Open the wrench menu, click Options, and select the Under the Hood tab.
  
  
• New blocked pop-up notification.
  The pop-up blocker formerly just minimized pop-up windows to the lower right corner of the browser window, create one 'constrained' window for each pop-up. Now, Google Chrome displays one small notification in the corner that shows the number of blocked pop-ups. A menu on the notification lets you open a specific pop-up, if needed.

Known Issues

• Sites that use Gears to synchronize offline data may occasionally hang. You should disable offline access for sites until a fix is released. (We're working on it and hope to have the update later this week.)

Security Issues

• This release fixes an issue with downloaded HTML files being able to read other files on your computer and send them to sites on the Internet. We now prevent local files from connectin to the network with XMLHttpRequest() and also prompt you to confirm a download if it is an HTML file.
  Severity: Moderate. If a user could be enticed to open a downloaded HTML file, this flaw could be exploited to send arbitrary files to an attacker.

For more details on what's changed and what issues are fixed, see the detailed release notes at http://dev.chromium.org/getting-involved/dev-channel/release-notes.

--Mark Larson, Google Chrome Program Manager

[NFGB] Link - from Google Chrome Releases Related From Google Blogs: Better Cooking Through Reader-ing What do Google Reader engineers read? We like it graphed Mixxx's Google Summer of Code 2008 Roundup Report