I have written a JavaScript bookmarklet that I use frequently for accessing computers on my local area network. A recent update to NoScript has blocked that bookmarklet (which used to work just fine), and after twiddling any setting in NoScript that looks like it might help, it is still being blocked.
Any idea what might have changed and whether/how I can whitelist this bookmarklet? I REALLY don't want to disable NoScript or uninstall it...
Thanks in advance!
Broken JavaScript BookMarklet SOLVED
Broken JavaScript BookMarklet SOLVED
Last edited by nsimbs on Fri Nov 03, 2017 2:17 pm, edited 1 time in total.
Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:56.0) Gecko/20100101 Firefox/56.0
Re: Broken JavaScript BookMarklet
*Always* check the changelogs BEFORE updating that important software!
-
Re: Broken JavaScript BookMarklet
Hmmm. So if I understand correctly, others have seen problems with bookmarklets since NoScript 5.1.4.
While they describe bookmarklets that are failing, I am not grokking their comments/observations. I didn't change any settings in NoScript, and I am not skilled enough to interpret why my bookmarklet started failing. From the comments in the two threads concerning a similar issue, I don't see a resolution, a workaround, nor an indication that one is being pursued.
Is this an issue the developer can address? Or do I "Enable Scripts Globally" when I want to run my bookmarklet? (Something I'd prefer not to do)
Thanks!
While they describe bookmarklets that are failing, I am not grokking their comments/observations. I didn't change any settings in NoScript, and I am not skilled enough to interpret why my bookmarklet started failing. From the comments in the two threads concerning a similar issue, I don't see a resolution, a workaround, nor an indication that one is being pursued.
Is this an issue the developer can address? Or do I "Enable Scripts Globally" when I want to run my bookmarklet? (Something I'd prefer not to do)
Thanks!
Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:56.0) Gecko/20100101 Firefox/56.0
Re: Broken JavaScript BookMarklet
Given Giorgio's comments in one of the other threads, you could try the following possible workaround -
1) Tools > Add-ons Manager > NoScript > Remove. If you get a warning, select "Yes, remove ALL protections"
2) Quit Firefox.
3) Start Firefox with the -purgecaches command-line switch: https://developer.mozilla.org/docs/Mozi ... ne_Options
Also clear the cache in Firefox in case that helps, I don't know whether it would or not.
4) Reinstall NoScript 5.1.4 from https://noscript.net/getit
5) Restart Firefox and check whether bookmarklets work.
If that doesn't fix it, I'm not sure what to suggest here, other than temporarily use an older version of NoScript.
Old NoScript @
https://addons.mozilla.org/addon/noscript/versions / https://addons.mozilla.org/addon/noscript/versions/beta
*or*
https://noscript.net/feed?c=100&t=a
1) Tools > Add-ons Manager > NoScript > Remove. If you get a warning, select "Yes, remove ALL protections"
2) Quit Firefox.
3) Start Firefox with the -purgecaches command-line switch: https://developer.mozilla.org/docs/Mozi ... ne_Options
Also clear the cache in Firefox in case that helps, I don't know whether it would or not.
4) Reinstall NoScript 5.1.4 from https://noscript.net/getit
5) Restart Firefox and check whether bookmarklets work.
If that doesn't fix it, I'm not sure what to suggest here, other than temporarily use an older version of NoScript.
Old NoScript @
https://addons.mozilla.org/addon/noscript/versions / https://addons.mozilla.org/addon/noscript/versions/beta
*or*
https://noscript.net/feed?c=100&t=a
*Always* check the changelogs BEFORE updating that important software!
-
Re: Broken JavaScript BookMarklet SOLVED
@barbaz : Your instructions are EXCELLENT!!
AND they worked, successfully resolving my problem.
Thank you very much!!
AND they worked, successfully resolving my problem.
Thank you very much!!
Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:56.0) Gecko/20100101 Firefox/56.0
Re: Broken JavaScript BookMarklet SOLVED
You're welcome! 
*Always* check the changelogs BEFORE updating that important software!
-