Google Chrome releases updates to different release channels. This developer preview channel ( Dev channel )is where ideas get tested (and sometimes fail). The Dev channel can be very unstable at times, and new features usually require some manual configuration to be enabled. Still, simply using Dev channel releases is an easy (practically zero-effort) way for anyone to help improve Google Chrome.
The Dev channel has been updated to 6.0.472.0 for Windows, Chrome Frame, and Linux. A Mac release will follow soon.This version come with Chrome Web Store( –enable-apps ) which is first announced by Google at the Google I/O conference in San Francisco on Wednesday.
The Chrome Web Store is Google’s forthcoming one-stop shop for Web-based apps, both free and paid.Web apps listed in the Chrome Web Store are regular web applications, built with standard web tools, they can be used by anyone using a modern browser that supports these web technologies.However users accessing the Chrome Web Store through Google Chrome will have the ability to create convenient shortcuts for easily accessing their apps.
one of the apps in Chrome
Chrome Dev 6.0.472.0 bug fix and New Features
Bugs fixed for All Platform
[r52790] Chromium stops saving files for any large downloads (Issue 49216)
[r52693] Fix crash with SSL client auth (Issue 49197)
[r52850] Option clicking a link now saves a resource directly without triggering a “Save As…” dialog (Issue 36775)
[r52911] Implement the upgrade available notification on the Wrench menu (Issue 45147)
[r52485] Implement the new, unified Wrench menu (Issue 47848)
[r52507] Fixed tab dragging glitches with newer GDEs (Issue 48774)
[r52729] Access GNOME Keyring on the main thread to fix a crash for some users (Issue 48343)
PDF plugin does not load on Linux (Issue 49702)
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