[CLOSED] Odd incompatibility with Tampermonkey extension
Posted: Sat Feb 18, 2017 11:17 am
I have found an incompatibility between NoScript and the update process within Tampermonkey (https://addons.mozilla.org/en-US/firefo ... permonkey/)
With NoScript running normally, the script update process in Tampermonkey does not work. However, if I allow scripts globally, then the script update process in Tampermonkey works just fine.
The issue exhibits itself as follows:
If I click on the update option within the Tampermonkey icon, then nothing happens. If I click the update option next to a specific script in the dashboard, then it says the check was successful, but it does not actually run (you can tell because it runs far too quickly).
Additional information:
* I am running the 64 bit nightly version of Firefox from 11th Feb (GB localisation) and have also tried the 32 bit version.
* I have tried NoScript 2.5.9.3 and 5.0rc2
* There are no entries in the console when I try to check for script updates
* I have tried removing my entire blacklist, just in case there was something in that.
* I have double checked that the 'chrome:', 'resource:' and 'moz-extension:' default entries are still in the whitelist.
Any ideas?
With NoScript running normally, the script update process in Tampermonkey does not work. However, if I allow scripts globally, then the script update process in Tampermonkey works just fine.
The issue exhibits itself as follows:
If I click on the update option within the Tampermonkey icon, then nothing happens. If I click the update option next to a specific script in the dashboard, then it says the check was successful, but it does not actually run (you can tell because it runs far too quickly).
Additional information:
* I am running the 64 bit nightly version of Firefox from 11th Feb (GB localisation) and have also tried the 32 bit version.
* I have tried NoScript 2.5.9.3 and 5.0rc2
* There are no entries in the console when I try to check for script updates
* I have tried removing my entire blacklist, just in case there was something in that.
* I have double checked that the 'chrome:', 'resource:' and 'moz-extension:' default entries are still in the whitelist.
Any ideas?