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.
Related posts:
Google Chrome To Get Automatic Userscript SupportGoogle Chrome 3 Adds Better Extension And Themes Support
Google Browser: Google Chrome And Chromium Download
One Step Closer To Extension Support In Google Browser
Google Chrome Nightly Builds Downloader
Google Chrome 2.0 Pre-Beta Release
Google Chrome Extensions Manager
Google Chrome And Firefox Extensions Differences
25 Responses to “Google Chrome Adds Greasemonkey Support”
Trackbacks/Pingbacks
-
[...] hier meer: Google Chrome Adds Greasemonkey Support Stem of voeg toe aan : chromium build, google [...]
-
[...] seriously. Recently they added local support for Greasemonkey in Google Chrome as pointed out by gHacks. As of build 3499 and onwards, all versions of Google Chrome will include Greasemonkey [...]
-
[...] [via gHacks] [...]
-
[...] to Martin at gHacks, the fact that Google doesn’t yet support an extension system within Chrome means that there are [...]
-
[...] to Martin at gHacks, the fact that Google doesn’t yet support an extension system within Chrome means that there are [...]
-
[...] GHacks announced that a basic version of Greasemonkey is now supported by a beta build of the Google [...]
-
[...] Google Hacks // [...]
-
[...] Martin explains in his blog, the script is set to work on every domain that are handled by the @include [...]
-
[...] GHacks Bitelia Etiquetas de : Google Chrome, Greasemonkey ← Anterior | Inicio Comparte esta [...]
-
[...] from gHacks writes “Only scripts in c:scripts are loaded and only if the user adds the parameter [...]
-
[...] a patch and it’s not yet clear if and when it will be part of the official Chrome release. As GHacks explains: Since there is no way of adding extensions to Chrome yet users have to live with some [...]
-
[...] Google’s latest beta release adds support for Greasemonkey. [...]
-
[...] Google 浏览器 Chrome 增加一个有趣的扩展，支持 Greasemonkey。因为目前没有办法在 Chrome [...]
-
[...] builds are said to have basic Greasemonkey support. With emphasis on basic. According to Martin at gHacks, the fact that Google doesn’t yet support an extension system within Chrome means that there are [...]
-
[...] Vía: GHacks [...]
-
[...] just a patch and it’s not yet clear if and when it will be part of the official Chrome release. As GHacks explains: Since there is no way of adding extensions to Chrome yet users have to live with some limitations. [...]
-
[...] Chrome可以看一下Google Chrome Greasemonkey这篇文章，Opera用户可以从Greasemonkey in [...]
-
[...] braucht die Greasemonkeyerweiterung für Mozilla Firefox. Google Chrome Anwender können sich den Google Chrome Greasemonkey Artikel ansehen der Informationen enthält wie man das Script in dem Browser anwenden kann. Opera [...]
-
[...] I use greasemonkey scripts from time to time, and greasemonkey isn’t built in yet, but you can enable it in some builds, with some caveats. Finally, I use firebug all the time when developing web pages. Chrome’s [...]
-
[...] Google Chrome users might get the script working in their web browser as well if they check the Google Chrome Greasemonkey [...]
-
[...] just a patch and it’s not yet clear if and when it will be part of the official Chrome release. As GHacks explains: Since there is no way of adding extensions to Chrome yet users have to live with some [...]
where frm u will get this beta build.
use SysInternal’s Junction to redirect c:\scripts to any other location.
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?
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.