Tampermonkey - 1.0.0.5

by derjanb
Bookmark and Share

A extension that provides Greasemonkey compatibility.

  • 1.0.0.5
  • GPL
  • derjanb
  • Visit Website
  • Visit Website
  • 1 Star2 Stars3 Stars4 Stars5 Stars (9 votes, average: 4.78 out of 5)
  • 15052 times

More about this extension

Tampermonkey is s small tools that provides enhanced Userscript support for Google Chrome and Chromium Browser (version 5.0.0.0 or greater). It’s API is fully compatible to GreaseMonkey. This means support of:
- all GM_* functions including:
  * GM_registerMenuCommand
  * GM_xmlhttpRequest with cross domain support
  * GM_getResourceText
  * GM_getResourceURL
- the tags:
  * @resource and 
  * @require 
- read access to variables of the unsafeWindow object
- access to functions of the unsafeWindow object (but there is no return value, sry).
Furthermore there is a small GUI to manage all installed scripts. This includes editing, enabling, disabling, debug, uninstalling and so on). By default one script is preinstalled that allows installing userscripts directly from userscripts.org.allows installing userscripts directly from userscripts.org.

Chrome/Chromium 5.0.0.0+ is required!

Known restrictions of version 1.0.0.5 and below:
- the "Allow access to file URLs" option must be set in order to install scripts from local ("file://") sources
- files with "*.user.js" ending are handled by chrome. rename your scripts to "*.tamper.js" to make tampermonkey take care of them
- due to chromes security model it is not yet possible to:
 * get the return value of javascript functions of the unsafeWindow object
 * write javascript vairables of the unsafeWindow object
- some scripts use very firefox specific methods, these script may not work in tampermonkey


Known restrictions of version 1.0.0.4 and below:
- BUG: it was not possible to install userscripts from http sources
- BUG: you have to enable TamperScript to install scripts from userscript.org
- BUG: some script may not run if there are multiple spaces in some places at the header tags

Change Log:

- Compatibility:
  * remove wrappedJSObj calls
  * emulate Obj.toSource()
- Bugs:
  * it was not possible to install userscripts from http sources
  * problems with multiple spaces in some header tags
  * GM_getResource didn't work on pages with flash
  * Tamperscript now is enabled by default
- Feature:
  * userscript source url is stored and used for update check
  * system script (Tamperscript) can't be deleted anymore
  * chrome extensions version supports file:// uri too 
    (Attention: a option needs to be enabled @ "chrome://extensions/")

Older Versions

  1. Version 1.0.0.0
    Compatible With
    Developer Builds
    Developer Builds (Linux)
    Beta Builds

    A small extension that provides Greasemonkey compatibility.

    Change Log:

    None

  2. Version 1.0.0.2
    Compatible With
    Stable Builds

    A small extension that provides Greasemonkey compatibility.

    Change Log:

     - add "file://*" permission to be able to install script from local sources 
     - overwrite Array.filter only in case the according compatibility option is set
     - fix "for each" replacement
     - split compatibility option into 4 more detailed options 
     - deny xmlhttpRequest access to urls not begining with "http" 

  3. Version 1.0.0.3
    Compatible With
    Stable Builds

    A small extension that provides Greasemonkey compatibility.

    Change Log:

     - support of read access to unsafeWindow variables
 - support @require tag
 - fix some bugs by unifying the script line endings
 - wait with contentscript execution until the document gets its first nodes added

  4. Version 1.0.0.4
    Compatible With
    Stable Builds

    A small extension that provides Greasemonkey compatibility.

    Change Log:

    - support of script running order
    - "new userscript" option
    - now one storage for every script is used independet from the url its running at
    - access to unsafeWindow functions (without return value)

Reviews

  1. Angel says:
    June 3, 2010 at 8:21 am

    Wonderful and easy to use the only thing would ask does this application bypass goggle security as if so then is not worth using

  2. derjanb says:
    June 3, 2010 at 8:32 am

    no, it does not bypass any of googles security features cause no javascript pointers are transfered from the unsafeWindow (they are stringified via JSON) and no access to file:// sources is possible when using GM_xmlhttpRequest.

  3. PERCE-NEIGE says:
    June 3, 2010 at 10:46 am

    Thank you. My life was empty without the userscripts.

  4. Angel says:
    June 5, 2010 at 7:27 pm

    Could you maybe give some scripts that work as I know colourful search works

  5. derjanb says:
    June 7, 2010 at 7:47 am

    There are a lot of script that are working. I’ve tested Tampermonkey with some Ikariam scripts, a Pennergame script, Google FX, “Last.fm – Get lyrics from lyricsplugin.com”, “Download YouTube Videos as MP4″ and so on…

  6. Gary says:
    October 10, 2010 at 6:18 pm

    This is absolutely fantastic. Why can I not find it on the official chrome extensions site? It’s not a complaint, just interested in the politics behind it.

  7. derjanb says:
    December 20, 2010 at 8:27 am

    You can find Tampermonkey here too.
    https://chrome.google.com/extensions/detail/dhdgffkkebhmkfjojejmpbldmpobfkfo?hl=de

    There are two extensions cause some time ago the permission to read local files required a manual review by the official chrome extension maintainers. This review would have taken some weeks., but now the user simply has to check a option to read local scripts. Now it doesn’t matter what extension you may install, cause they’re equal beside the extension ID.

Write a Review