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.

{via ghacks}