Beoardielingen foar NoScript Security Suite
NoScript Security Suite troch Giorgio Maone
Wurdearringen foar Firefox-brûker 14275679
Wurdearring: 5 fan 5
troch Firefox-brûker 14275679, 7 jierren lynUPDATE: It seems, although the Firefox add-ons page was reporting NoScript 10.1.9.4 it may not have been that version causing the issues, although Firefox had been re-started 3 times. Since writing the report (and those 3 re-starts after NoScript updated), the local page issues have now gone. Maybe 10.1.9.4 has to be run more than once for its fixes to the 10.1.9.2 bugs to take effect, and these are only picked up on browser re-start? The incorrect display of < noscript > has gone on the 4th re-start and the NoScript menu now shows a configurable file: domain for the first time since the major upgrade. Thank you for fixing! Changed from 1* to 3* [will be back to 5* if/when fully working].
FURTHER UPDATE: It has been working ok the rest of the day, so looks like the general incompatibility with Firefox 62.0 has also been fixed. Now back to 5* thanks.
ORIGINAL ISSUES [now fixed]:
As others have found, Firefox 62 plus the bad and admitted severe bugs in NoScript 10.1.9.2 have totalled its operation and the only way of using Firefox is to disable NoScript. Where do I start? All issues have been verified by disabling NoScript: without it no issues occur, with it enabled all occur, so it is the sole cause.
First, after a while, as others have reported, Firefox just stops working and will show nothing. From the console, it looks like NoScript has broken the Firefox origin policy on everything. Where is it trying to import scripts from?
The problem, reported on the NoScript forum that pages on local disks are broken since 10.1.9.2 on Firefox 61.0.2 remains. The scripts (used to) run but incorrectly also showed the content of < noscript >. A moderator proved this with a use case but the report has now been deleted. In Firefox 62.0, it is now worse. The page may load once (incorrectly) if you are lucky, then if you reload it stops (previous point). There is no facility in the current UI to specify permission for local pages (I think there was before the big change to the Firefox api)
Somewhere, probably in 10.1.9.2, the user list of allowed and blocked sites has been corrupted. 10.1.9.4 was supposed to fix this and recover the situation but hasn't [on the first or second runs].
As you just seem to delete some issues reported on your forums, please don't ask me to post there. Unless this barrage of severe errors is fixed quickly, the product is now unusable, sorry. I will be sad to have to uninstall it after around 5 years.
FURTHER UPDATE: It has been working ok the rest of the day, so looks like the general incompatibility with Firefox 62.0 has also been fixed. Now back to 5* thanks.
ORIGINAL ISSUES [now fixed]:
As others have found, Firefox 62 plus the bad and admitted severe bugs in NoScript 10.1.9.2 have totalled its operation and the only way of using Firefox is to disable NoScript. Where do I start? All issues have been verified by disabling NoScript: without it no issues occur, with it enabled all occur, so it is the sole cause.
First, after a while, as others have reported, Firefox just stops working and will show nothing. From the console, it looks like NoScript has broken the Firefox origin policy on everything. Where is it trying to import scripts from?
The problem, reported on the NoScript forum that pages on local disks are broken since 10.1.9.2 on Firefox 61.0.2 remains. The scripts (used to) run but incorrectly also showed the content of < noscript >. A moderator proved this with a use case but the report has now been deleted. In Firefox 62.0, it is now worse. The page may load once (incorrectly) if you are lucky, then if you reload it stops (previous point). There is no facility in the current UI to specify permission for local pages (I think there was before the big change to the Firefox api)
Somewhere, probably in 10.1.9.2, the user list of allowed and blocked sites has been corrupted. 10.1.9.4 was supposed to fix this and recover the situation but hasn't [on the first or second runs].
As you just seem to delete some issues reported on your forums, please don't ask me to post there. Unless this barrage of severe errors is fixed quickly, the product is now unusable, sorry. I will be sad to have to uninstall it after around 5 years.
2.417 beoardielingen
- Wurdearring: 5 fan 5troch Firefox-brûker 19487299, ien dei lyn
- Wurdearring: 5 fan 5troch Ryan Steed, 11 dagen lyn
- Wurdearring: 2 fan 5troch Wewe Never, 11 dagen lynIt doesnt remember changed levels, and 90% of all sites i visit needs permission. Javascript is everywhere I guess. Deleted the addon.
Antwurd ûntwikkeler
11 dagen lyn pleatstIf you flag sites as TRUSTED rather than Temp. TRUSTED, permissions are remembered. Otherwise it's a bug, probably with your browser configuration, and should reported at github.com/hackademix/noscript/issues thanks. - Wurdearring: 5 fan 5troch ZeroUnderscoreOu, 21 dagen lyn
- Wurdearring: 5 fan 5troch 鼎针皮艺, ien moanne lyn
- Wurdearring: 5 fan 5troch Bob, ien moanne lyn
- Wurdearring: 1 fan 5troch mlatpren, ien moanne lynIt does a great job at blocking, but is regularly frustrating with re-enabling things. It's supposed to show you what it's blocking, but that's extremely hit-or-miss. Occasionally, there'd be something blocked where the only solution is to disable the extension. As in, right-click and disable *from Firefox itself.*
- Wurdearring: 3 fan 5troch zekromVale, ien moanne lynThere needs to be a CPU limit on this extension, using 30% CPU of an intel i7 11th gen laptop CPU on YouTube is ridiculous. Firefox for Ubuntu snap, flatpack, or just .deb are affected. Must disable NoScript to fix it or allow everything fully for all domains on the page. I would like more domains to be added to the global trusted list though (by default) or have a popup at the top when you first visit a page.
- Wurdearring: 5 fan 5troch Hopeavirta, 2 moannen lyn
- Wurdearring: 5 fan 5troch Lazy Cat, 2 moannen lyn
- Wurdearring: 5 fan 5troch sumobunny, 2 moannen lyn
- Wurdearring: 5 fan 5troch Zelgadis-San, 2 moannen lyn
- Wurdearring: 5 fan 5troch Dadou, 2 moannen lyn
- Wurdearring: 3 fan 5troch aq, 2 moannen lynUser for at least 15 years, Something is conflicting on Firefox. It is blocking scripts and other add ons such as tampermonkey or violentmonkey with scripts added, but without any listing of what is being blocked. Only option is to shut it off to proceed.
Even blocking games internal scripts without any 'monkey' in use.
Please check and test - Wurdearring: 5 fan 5troch Simon Bünemann, 2 moannen lyn
- Wurdearring: 5 fan 5troch ADKFZ8O, 2 moannen lyn
- Wurdearring: 5 fan 5troch Marw, 2 moannen lyn
- Wurdearring: 1 fan 5troch aedgsegsfvw, 3 moannen lynWARNING! Causes crashes with SEVERE data loss. Since mid 2025, this extension regularly causes the browser to crash. It can even crash the browser so severely that windows freezes irreversibly, with SEVERE data loss as a result. The crashes stopped when I deleted this extension, and re-occurred after reinstalling it. Several others have reported the same issues on user forums.
- Wurdearring: 2 fan 5troch Firefox-brûker 15990777, 3 moannen lyn
- Wurdearring: 5 fan 5troch Arman Daneshjoo, 3 moannen lyn
- Wurdearring: 5 fan 5troch elmika, 3 moannen lyn
- Wurdearring: 5 fan 5troch Firefox-brûker 19469020, 4 moannen lyn
- Wurdearring: 5 fan 5troch Firefox-brûker 14500718, 4 moannen lyn
- Wurdearring: 5 fan 5troch Firefox-brûker 19459487, 4 moannen lynI'm notified every time WebGL is blocked on each page load. There's no way to disable these notifications and it's very irritating.
Edit: updated to 5 stars as it can be disabled after all but the setting isn't described very clearly.Antwurd ûntwikkeler
4 moannen lyn pleatstYou should not get any notification. Just a little placeholder inside the page, to be able to enable it back. And you can disable it by unchecking "NoScript Options>Appearance>Show synthetic placeholders for invisible capability probes"