Friday, August 12, 2011

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

7 comments:

  1. Anonymous12 August, 2011 08:05

    This comment has been removed by a blog administrator.

    ReplyDelete
  2. Anonymous13 August, 2011 09:34

    Mh, and for iceweasel 3.5.16 on débian stable suqueeze?

    The 0.9.8 of greasmonkey does't work :|

    ReplyDelete
  3. Anonymous17 August, 2011 01:17

    why not use the scrip just say no for grasemonkey

    ReplyDelete
  4. Anonymous18 August, 2011 03:15

    Kindly add/modify sample code on http://wiki.greasespot.net/GM_xmlhttpRequest for progress event.

    ReplyDelete
  5. arantius19 August, 2011 07:26

    Mozilla has suddenly decided to block for a few particular code issues, rather than just warn as they always have. This version is delayed.

    ReplyDelete
  6. Peter19 August, 2011 19:32

    Why doesn't @run-at document-start run in frames??
    I really would like to use the feature but I have to support frames... :/

    ReplyDelete
  7. Peter19 August, 2011 20:06

    I just realized, the new @run-at document-start enables homepage owners to disable userscripts quite easily if the scripts rely on it. Simply use frames and the script is toast. >_<

    ReplyDelete