Monday, August 01, 2011

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).
at

8 comments:

  1. Anonymous01 August, 2011 23:46

    PLEASE, make a Firefox version 8 compatible Greasemonkey!

    ReplyDelete
  2. Anonymous06 August, 2011 13:46

    I need to run a GM script on a FF about: page, which is said to be fixed in the 0.9.8 release; however, the FF extension page still only has the 0.9.7 version. :-( Where do I get the latest release? Thanks.

    ReplyDelete
  3. arantius07 August, 2011 09:24

    Anon:

    If you're going to run pre-alpha software (6 is now beta, 7 alpha, 8 pre-alpha), you need to learn how to help yourself. Use the Add-on Compatibility reporter, or use stable software.

    ReplyDelete
  4. Anonymous08 August, 2011 01:00

    One thing to add from Sriptish is GM_setClipboard, that would be very useful :)

    ReplyDelete
  5. Anonymous11 August, 2011 17:48

    Whoa! A little brutal to remove support for FF < 3.6!
    Debian testing still uses 3.5.19 and I would guess there's a few of us in that boat out here on the intertubes!

    ReplyDelete
  6. Anonymous11 August, 2011 23:53

    I still use 3.5 because 3.6 is unstable for me and I can't trust the newer versions. Memory issues that got worse in 4.0 won't be fixed until 7.0 is released, and there's no telling how long it will be before it's back down to 3.5's levels.

    It's way too soon to pull the plug on 3.5.

    ReplyDelete
  7. Anonymous13 August, 2011 05:18

    I'm another debian user that is stuck on 3.5. This is painful.

    ReplyDelete
  8. Anonymous26 August, 2011 11:21

    This is a one of my most essential addons. Great work! But the last upgrade to 0.9.8 broke it on my browser (firefox 3.5.16). If you don't support stable browsers anymore could you please at least remove version 3.5 from the compatibility list on addons.mozilla.org to prevent greasemonkey to update to a broken version on this browser. Thanks!

    ReplyDelete