Google Chrome Adds Greasemonkey Support

One of the elementary things that the Google browser is missing is support for some kind of plugins or extensions that Firefox offers for a long time. Google announced plans to support an extension API in later builds of the web browser but it currently lacks that support and that could be one of the reasons why many users shy away from the browser. That and the fact that the browser is still looking to the outside like a very early beta build.

One interesting addition to the latest beta builds of the Google Chrome browser was basic Greasemonkey support. Since there is no way of adding extensions to Chrome yet users have to live with some limitations. Only scripts in c:\scripts are loaded and only if the user adds the parameter –enable-greasemonkey by appending it to the program’s shortcut.

There is another serious limitation. The scripts are not limited to a domain but will work on all domains which is usually handled by the @include metadata. The metadata part is ignored which could be problematic when loading some Greasemonkey scripts.

Greasemonkey support was added in build 3499 which is available from the Chromium build ftp. Support is also included in later builds including the latest Google Chrome 3601 build.

Tags: chrome browser, chromium, chromium build, Google, google browser, google chrome, greasemonkey, greasemonkey support
Categories: Browsing, Google Chrome

Related posts:

1. Google Chrome 4 Natively Supports Greasemonkey Scripts
2. Google Chrome 3 Adds Better Extension And Themes Support
3. Google Chrome To Get Automatic Userscript Support
4. Google Browser: Google Chrome And Chromium Download
5. One Step Closer To Extension Support In Google Browser
6. Google Chrome 2.0 Pre-Beta Release
7. AM-DeadLink 4 Beta Adds Google Chrome Support
8. Google Chrome Adblocker

28 Responses to “Google Chrome Adds Greasemonkey Support”

1. markandey singh says:

   October 19, 2008 at 10:48 pm

   where frm u will get this beta build.

   Reply
2. Alex says:

   October 20, 2008 at 12:35 am

   use SysInternal’s Junction to redirect c:\scripts to any other location.

   Reply
3. movie fan says:

   November 22, 2008 at 3:04 am

   I hesitate to use even upgraded versions of Chrome, since my last experience using it (first version) left my computer compromised; have they fixed the security issues beyond all doubt?

   Reply
4. mystylplx says:

   April 3, 2009 at 8:18 pm

   It doesn’t work. Greasemetal worked until the latest update (developer trunk) but now it doesn’t work either. But greasemonkey with the -enable-greasemonkey argument never worked on any build for anyone I know.

   Reply
5. Pittie says:

   December 22, 2009 at 8:32 pm

   I managed to get GM scripts working finally… Thanks to the above info and this tutorial…

   http://jaxov.com/2009/11/install-greasemonkey-scripts-in-google-chrome-easily/

   Reply
6. Gia says:

   January 1, 2010 at 8:26 pm

   I found this post really helpful regarding Grease monkey support in Chrome
   http://www.crispytech.com/2010/01/01/install-greasemonkey-userscripts-chrome/

   Reply