Monday, April 23, 2012

Greasemonkey Release 0.9.19

The entire list of bugs handled in this release is also available via the 0.9.19 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:
  • A custom wrapper to make setTimeout() work even when Javascript is disabled. (#1209)
  • Restored the "script installed successfully" toast notification. (#1511)
  • Scripts download more incrementally; the install dialog should appear as soon as the script metadata has been downloaded, not after the entire script is downloaded.  (#1523)
Bug fixes:
  • Specifying a script editor in a non-ASCII folder will work (Firefox 4+ only). (#1173)
  • Scripts installed while the Add-Ons Manager is open will show their icon. (#1535)
Plus a variety of minor code cleanups and enhancements behind the scenes.

Tuesday, February 28, 2012

Greasemonkey 0.9.18 Release

The entire list of bugs handled in this release is also available via the 0.9.18 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:
Bug fixes:
  • Add-on Manager shows correct data when re-installing (e.g. to update) a script. (#1476)
  • Re-installed scripts are put into the same directory as the original. (#1515)
  • The matches property of GM_info is now a list of (pattern) strings. (#1516)

Automatic script updates come to Greasemonkey

In the 0.9.18 release, Greasemonkey is now checking for, and installing, updated versions of user scripts by default.  This post is intended as a primer for how this new functionality works, both for users and for script authors.


The Greasemonkey Options dialog now includes these settings to control automatic update checking and installation. By default updates will be checked for every seven days, and automatically installed when found.  The download location must be secure (https) by default.  And it should just work!

If you know there's an update, you can open the Add-ons manager, right click on a User Script, and choose "Find Updates".  This will check immediately, even if a scheduled check has happened more recently than seven days ago.*

*You may need to clear your browser cache, if an old version of the script was downloaded recently.

Script Authors
Greasemonkey supports a number of new metadata directives to support updates: @downloadURL, @updateURL and (more than before) @version.

The @updateURL will be accessed when checking for the update.  This can be a ".meta.js" format like userscripts.org produces, with only the metadata.  The @version defined here will be checked to the install version.  It does not need to be hosted on https to be checked by default.

Sidebar: for userscripts.org, the updateURL is automatically set to the .meta.js corresponding to the script, and passed through the Coral Content Distribution Network (see why).

The @downloadURL is where the update will be downloaded from, when found.  This is most useful to guarantee that updates come from a secure (https) location, so that they will be installed by default.

If @updateURL or @downloadURL are not provided, the URL that the script was downloaded from is used instead.  If the @downloadURL is not provided and the install URL is not known, updates will never be applied.

Finally the @version directive controls what is considered an update.  Read about the (Mozilla) toolkit version format to learn exactly what value is greater than what, and what formats are valid.

It's also worth pointing out that the recently added GM_info API can be used to check if Greasemonkey will ever try to apply updates (e.g. because the user has turned it off, or the URL is insecure).

Finally, if you want to make sure that Greasemonkey will never update your script, it can be accomplished by providing an invalid @updateURL (like "about:blank") which will never return a newer version.

Questions?
Please bring any questions or comments to us at the greasemonkey-users discussion list.

Saturday, February 11, 2012

Greasemonkey 0.9.17 Release

Whoops, there was a problem with 0.9.16 yesterday, so here's a quick patch.

Bug fixes:
  • Error: "aForced is not defined".  (#1517)

Friday, February 10, 2012

Greasemonkey 0.9.16 Release

The entire list of bugs handled in this release is also available via the 0.9.16 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:
  • Expose information (including Greasemonkey version) to user scripts via GM_info. (#1452; also see #1512)
  • Track the install time of scripts.  (This is designed to better support automatic updates for scripts ... still coming soon.)  (#1513)
Bug fixes:
  • Editing script from the "New User Script" feature, to change any remote dependency (@icon, @require, @resource), could the script to malfunction. (#1504)
  • Enabling/disabling scripts from the status bar menu (Firefox 3 only). (#1506)
  • Incompatibility with GreaseFire.  (#1507)
  • Failures during "Check for Updates" from the Add-on manager. (#1509)

Wednesday, January 25, 2012

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)

Friday, January 20, 2012

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)

Thursday, November 03, 2011

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)

Friday, October 28, 2011

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.

Friday, October 21, 2011

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.

Thursday, September 29, 2011

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)

Friday, September 23, 2011

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.

Tuesday, September 06, 2011

Greasemonkey 0.9.11 Release

The entire list of bugs handled in this release is also available via the 0.9.11 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:
  • Work around for a problem Tab Mix Plus causes when opening links in new tabs. (#1406)

Monday, August 22, 2011

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)

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)

Friday, August 05, 2011

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.

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

Thursday, July 14, 2011

Greasemonkey 0.9.7 Release

Bug fixes:
  • Scripts with broken @icons will install, just with no icon. (#1214)
  • Editing the @icon line of a script will take effect immediately. (#1215)
  • Remote resources (@require, @resource, @icon) that redirect to other URLs will now work. (#1222)
Enhancements:
  • Compatibility with Firefox 6 and 7. (#1357)
  • GM_openInTab() will respect the insertRelatedAfterCurrent preference. (#1370)
The entire list of bugs handled in this release is also available via the 0.9.7 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).

Friday, July 08, 2011

Greasemonkey Usage by Firefox Version, July 2011

I wrote a very similar post three months ago, but there's been a lot of real motion along Mozilla's fast release track since then. It's worth revisiting these numbers:Click for a larger image, or browse the data in Google Docs, with a larger view and a line chart as well.

This stacked area chart makes a few of trends obvious: Firefox 4 became very popular over its short life, and Firefox 5 is quickly replacing it. But also: Firefox 3.6 is definitely still kicking, at the second most common browser over the past week. Here's some data; the average daily usage for each version over the past week:
  • 5.0 1,589,647
  • 3.6 798,062
  • 4.0 461,349
  • 3.0 150,314
  • 3.5 117,740
  • 2.0 13,144
  • 6.0 2,596
  • 7.0 1,990
  • 1.5 392
Or: Version 3.x (1,066,116) is still one third of total usage (3,135,233). And even if 4.0 is dropping quickly, right now it's still almost a quarter of the total post-3 users.

Friday, June 24, 2011

Greasemonkey 0.9.6 Release

Bug fixes:
  • GM_openInTab() fails in Firefox 3. (#1361)
  • Firefox 5: Error in Add-ons Manager. (#1367)
Enhancements:
  • Add "get user scripts" link to the Add-ons Manager. (#1213)
  • Pass site cookies when downloading scripts. (#1359)
The entire list of bugs handled in this release is also available via the 0.9.6 milestone on GitHub. Note that as always it takes some time for Mozilla to review the new version, and it's available on the all versions page. 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).
 
国产野外无码理论片在线观看_国产亚洲中文日本不卡二区_国产亚洲欧美在线观看一区