Greasemonkey support added to Google Chrome

We had posted about “Greasemetal” that brings Greasemonkey-like functionality on Chrome. Now a recent build of Chromium added user scripts support to Google Chrome, contributed by Aaron Boodman. For now, the support is limited: Chromium reads the scripts from the hard-coded directory c:\scripts and it ignores the @include metadata which restricts scripts to one or more web addresses. […]

We had posted about “Greasemetal” that brings Greasemonkey-like functionality on Chrome. Now a recent build of Chromium added user scripts support to Google Chrome, contributed by Aaron Boodman. For now, the support is limited: Chromium reads the scripts from the hard-coded directory c:\scripts and it ignores the @include metadata which restricts scripts to one or more web addresses. To enable Greasemonkey support, you need to use the flag: --enable-greasemonkey, for example by appending it to the target of a shortcut.

The latest Chromium snapshots are available at the BuildBot site, but they don't support Google's auto-updater and they're less stable than the official releases. You only need to download the file chrome-win32.zip from the most recent folder.

Source:→ Google System