Greasemonkey 0.9.15 Release

The entire list of bugs handled in this release is also available via the 0.9.15 milestone on GitHub. Note that as always it takes some time for Mozilla to review the new version, but it's available on the all versions page immediately.

If you are using it and notice problems, it's best to log an issue or let us know at greasemonkey-dev (and be clear that it's with this version).

This release was hurried, to resolve a few serious bugs introduced in 0.9.14. A few other bugs were also fixed.

Bug fixes:

• Editing an installed script to change any remote dependency (@icon, @require, @resource) could cause one or many scripts to be deleted. (#1466, #1502)
• Certain @requires can break a script, due to javascript semicolon insertion rules.  (#1491)
• Toggling the enabled state of a script via the main (Tools > Greasemonkey) menu failed on Mac.  (#1496)
• Installing a script from local disk failed in 0.9.14.  (#1501)

Greasemonkey 0.9.14 Release

The entire list of bugs handled in this release is also available via the 0.9.14 milestone on GitHub. Note that as always it takes some time for Mozilla to review the new version, but it's available on the all versions page immediately.

If you are using it and notice problems, it's best to log an issue or let us know at greasemonkey-dev (and be clear that it's with this version).

Enhancements:

• For new script installs, and installed scripts' updates (still not enabled by default) there is a progress meter for the download. (#1419)

Bug fixes:

• Revert the changes to GM_xmlhttpRequest() in 0.9.13 (which were supposed to have no effect, but created a subtle bug). (#1472)
• Guarantee that we do not create a specific kind of memory leak.  (#1482)

Greasemonkey 0.9.13 Release

The entire list of bugs handled in this release is also available via the 0.9.13 milestone on GitHub. Note that as always it takes some time for Mozilla to review the new version, but it's available on the all versions page immediately.

If you are using it and notice problems, it's best to log an issue or let us know at greasemonkey-dev (and be clear that it's with this version).

Enhancements:

• Script updates install automatically. (#1442)
  In 0.9.12 we added update checking.  In 0.9.13 updates install automatically, but there's still some discussion over how to handle this best (#1455), so checking is still not enabled by default.  We hope to figure this out by the 0.9.14 release.  Some other update related work was done, mostly to make Firefox 3 work better.  (#1421, #1422, #1423)
• Provide an Options item in the Monkey Menu. (#1447)
• Add a Cancel button to the Options window. (#1454)

Bug fixes:

• GM_getResourceText() was broken. (#1438)
• You can properly select an application (bundle) for the editor on Mac OS X.  (#1439)
• Fix GM_openInTab() for Firefox 3. (#1444)
• Fix when pages reassign the location during page load. (#1445)

Greasemonkey Usage by Firefox Version, Oct 2011

Just like August's post, here's a graph of what versions of Firefox people use Greasemonkey with.



You can open the spreadsheet for the raw data and a larger graph.

Takeaways seem to be not a lot has changed, besides some up-and-down for each rapid release version since then (6 came and went, with 7 replacing it).  Firefox 3.6 users are still just shy of three quarters of a million.  Firefox versions too old for the newest version of Greasemonkey are still hanging in at almost a quarter million, and just shy of 50,000 users are running a too-new version of Firefox, probably with Add-on Compatibility Reporter.

Greasemonkey 0.9.13 beta1

Greasemonkey release 0.9.13 should include complete automatic in-the-backgroudn updating of user scripts.  As yet there are no docs for script authors but the short version is: put an @version in your metadata, and increase it when there is an update.

Greasemonkey 0.9.13 beta1 is now available for testing.  It's in the Mozilla Add-ons beta channel. Open the "Development Channel" drop down at the bottom of the page, and click the "Add to Firefox" button.

Please report an issue or find us at the mailing list to provide feedback on beta versions.

Greasemonkey 0.9.12 Release

The entire list of bugs handled in this release is also available via the 0.9.12 milestone on GitHub. Note that as always it takes some time for Mozilla to review the new version, but it's available on the all versions page immediately.

If you are using it and notice problems, it's best to log an issue or let us know at greasemonkey-dev (and be clear that it's with this version).

Enhancements:

• Script update checking (limited!). (#1053)
  We have started to build script update checking.  In 0.9.12, it is never automatic in the background.  You may choose to check one script (right click and choose "Find updates") or all scripts ("Check for updates" in the tool menu near the top of the Add-ons Manager).  If updates are found they will then be displayed.  Please use this feature and let us know if it works well, or if it breaks somehow.  Once we're confident that it works, we'll turn it on by default (automatically checking in the background) in a future release.
• Scripts run with the latest available version of Javascript. (#1403)

Bug fixes:

• Shared window object. (#1278)
  Before 0.9.0, it was possible to set properties on the window object, and other scripts would be able to read those properties.  This behavior was never supported, but as the compatibility fix that broke it is no longer necessary, it has been reverted.  It is still not suggested that you leverage this quirk, it is not a fully supported feature and may break again in the future.
• Right-clicking a script in the Monkey Menu works, even when no editor is configured.  (#1405)
• Fix launching the editor.  (#1409)
• Scripts with @match could break loading all other scripts.  (#1414)
• When browsing local files, menu commands for all scripts (on all tabs) no longer display.  (#1424)
• Fix GM_openInTab(). (#1428)

Try the Greasemonkey 0.9.12 beta!

We've fixed a few bugs and started working on auto-updates for scripts. Please, if you have a chance, download the beta release and test things out.

It's available in the Mozilla Add-ons beta channel. Open the "Development Channel" drop down at the bottom of the page, and click the "Add to Firefox" button.

Please report an issue or find us at the mailing list to provide feedback on beta versions.