krotlibrary.blogg.se

Fixing greasemonkey scripts for current version of firefox
Fixing greasemonkey scripts for current version of firefox











  1. #Fixing greasemonkey scripts for current version of firefox how to#
  2. #Fixing greasemonkey scripts for current version of firefox download#

Locate Profile Folder and click Open Containing Folder, this should open the folder in the standard file manager. This works for Firefox 3.6 and newer only.

#Fixing greasemonkey scripts for current version of firefox download#

I'll either do what I last mentioned and simply download everything automatically and have it cleared out once per day automatically, or get a greasemonkey script to kill these prompts, or find a way to hack Firefox to remove the downloading functionality from the browser entirely. The easiest way to find the location of the Firefox profile folder is to enter about:support in the address bar. And this little issue I have here, I'll figure it out eventually. Users who want to do that need to locate the Firefox profile folder on the hard drive. There is a way to uninstall Firefox add-ons and userscripts directly without starting the browser. This lasts only until the next restart when the script appears again in the listing. More information can be found on the scripts GitHub page. Uninstall any previous versions of the script and/or niknahs KoCAttack script. Install/upgrade to latest versions of Firefox and Greasemonkey.

#Fixing greasemonkey scripts for current version of firefox how to#

The userscripts are displayed just fine on the about:addons page, and a click on Remove confirms that the script has been removed. Adobe Flash Version 10.3.183.90 Firefox 9.0.1 Greasemonkey 0.9.22.1 Once youve got the above installed, open this link in Firefox to install the script. Heres how to solve 99 of the errors people report with this script: 1. But it may also be related to Firefox since the browser is a development build as well. The Greasemonkey version available for Firefox is a development build, and it may be that this is the cause for the removal problems. I'm currently testing the latest builds of the upcoming Firefox 4 browser and noticed that it is not possible to uninstall Greasemonkey userscripts using the standard controls in the browser at the time of writing. So, in conclusion, the extension version (if properly developed) always performs better than the userscripts, but the difference is insignificant, so users should pick the one they like the most.Most Firefox users remove add-ons and userscripts from within the web browser.

fixing greasemonkey scripts for current version of firefox

While my extension only has to check if the current page is the one I allowed it to run and then run the extension, the userscript needs to go through the same thing and check for the permissions and act as the middle man between the userscript requests (if there are any) and the browser api.Īnd I am not here taking into account the ongoing E10 shifty support between both sides, I've had these results before that. Now, to what you actually asked: during my tests I found that the performance difference was negligible, with the obvious advantage to the dedicated extension version because any userscript manager ALWAYS adds overhead due to the parsing and api permissions. Since I found that the userscript version was capable of offering everything the features needed (this was something I made sure of and still keep doing so, both versions must have the same features), I decided to release in both versions so both types of users could pick what they prefer best. If you have Greasemonkey installed and not blocked automatic add. On the other hand, those users that never installed greasemonkey (or similar) prefer to install another add-on, period, instead of another add-on (greasemonkey) just to install the userscript. Today's Greasemonkey 1.0 release fixes the issue, just in time for the release of Firefox 15 to prevent Firefox users switching to the latest stable version of the browser to experience memory leaks in a version of the browser that was designed to prevent those leaks from happing. People that already have greasemonkey installed (or similar userscript manager) usually prefer to install another userscript instead of another add-on, with me being one of those examples. As the developer of the second (better yet, third?) link in your example, my main reason for offering both versions is simple:













Fixing greasemonkey scripts for current version of firefox