Greasemonkey 0.9.10 Release

The entire list of bugs handled in this release is also available via the 0.9.10 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 either let us know at greasemonkey-dev or log an issue (and be clear that it's with this version).

Bug fixes:

• You will be prompted to pick a new editor if the existing setting is an invalid path. (#1386)
  
• Changing views within the Add-ons Manager could cause the user script sort order to be wrong. (#1394)
  

Enhancements:

• When a script causes an unhandled error, the display in the Error Console will be a bit easier to read. (#1396)
• When Growl is not installed, Greasemonkey's notifications are less obtrusive. (#1397)
• A range of internal code clean ups. (#1395, #1398, #1399, #1400, #1401)
  

Greasemonkey 0.9.9 Release

Update: Mozilla did not pass this version for review. Since 0.9.10 was already underway, their requested changes were made there. This version never really hit a public release.

The entire list of bugs handled in this release is also available via the 0.9.9 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 either let us know at greasemonkey-dev or log an issue (and be clear that it's with this version).

Bug fixes:

• Pressing 'back' could rarely cause a script to run twice on the same page. (#1083)
• Extended characters would get corrupted in new scripts. (#1236, #1315)
  
• A full disk could cause loss of data (especially config.xml). (#1301)
• (Affecting 0.9.8) Scripts would not install (all scripts in Firefox 3: #1389, always for certain scripts: #1391)
  

Enhancements:

• GM_xmlhttpRequest() provides progress events. (#1081)
• GM_xmlhttpRequset() provides a synchronous mode. (#1269)
• By popular demand: a UI for editing @includes and @excludes. (#1362)
  

Greasemonkey Usage by Firefox Version, August 2011

I'm revisiting the Greasemonkey usage topic. A short while back, we decided to drop support for Firefox 3.0 from new versions of Greasemonkey, somewhat based on the similar work I did back then. But I realize that last graph wasn't very well done, it didn't reveal the 3.x usage clearly. So here's an interactive trend graph that makes it much more obvious:


(Access the raw data and a larger graph at Google Docs.)

It turns out that Firefox 3.5 is even less used than 3.0, both well under 5%. On the other hand, as mentioned, 3.6 is still 25% of usage. It may well mean that we drop 3.5 support and take advantage of some of the behind-the-scenes things available only in 3.6 and higher very soon.

P.S. There's also some graphs, by major version, and minor version within 0.9, of Greasemonkey usage.

Nerd alert: To make this graph, I started with the AMO statistics, and passed it through a python script to clean up and combine the (patch level) versions. By hand, I rearranged the data into a 7-day moving average for the versions I was interested in: 3.0 and higher.

Greasemonkey 0.9.8 Release

Bug fixes:

• User scripts cannot run in any about: pages besides about:blank. (Security enhancement; #1375)
  

Enhancements:

• Global, user specified, @exclude rules. (#1002)
• New @run-at metadata imperative, which supports value document-start, as well as the standard document-end behavior. Please see the documentation. (#1103)
• Support for @match metadata imperative, as implemented by Google Chrome. Thanks to Scriptish for original implementation. (#1377)
• Support for full regular expression syntax in @include/@exclude rules. Please see the documentation. (#1378)
  

The entire list of bugs handled in this release is also available via the 0.9.8 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 either let us know at greasemonkey-dev or log an issue (and be clear that it's with this version).