Omtaler for NoScript Security Suite
NoScript Security Suite av Giorgio Maone
Omtale av Firefox-bruker 14275679
Vurdert til 5 ut av 5
av Firefox-bruker 14275679, 7 år sidenUPDATE: 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 419 omtaler
- Vurdert til 4 ut av 5av Firefox-bruker 18127040, 4 dager sidenТакие прям зайки и лапочки... Разместить закрытие окна приветствия и "Пожертвовать" чуть ли не с наложением друг на друга. Эдакое "Ну, даааааайти деняяяяяях!". Звезда в минус.
Аддон классный, но не нужно быть, как эти. - Vurdert til 4 ut av 5av MinorityMaid, 4 dager sidenIt's extremely useful, but not exactly intuitive.
- Vurdert til 5 ut av 5av Sunny, 5 dager siden
- Vurdert til 5 ut av 5av Firefox-bruker 19664008, 14 dager siden
- Vurdert til 5 ut av 5av Firefox-bruker 19487299, 16 dager siden
- Vurdert til 5 ut av 5av Ryan Steed, én måned siden
- Vurdert til 5 ut av 5av ZeroUnderscoreOu, én måned siden
- Vurdert til 5 ut av 5av 鼎针皮艺, én måned siden
- Vurdert til 5 ut av 5av Bob, 2 måneder siden
- Vurdert til 1 ut av 5av mlatpren, 2 måneder sidenIt 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.*
- Vurdert til 3 ut av 5av zekromVale, 2 måneder sidenThere 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.
- Vurdert til 5 ut av 5av Hopeavirta, 2 måneder siden
- Vurdert til 5 ut av 5av Lazy Cat, 2 måneder siden
- Vurdert til 5 ut av 5av sumobunny, 2 måneder siden
- Vurdert til 5 ut av 5av Zelgadis-San, 2 måneder siden
- Vurdert til 5 ut av 5av Dadou, 2 måneder siden
- Vurdert til 3 ut av 5av aq, 2 måneder sidenUser 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 - Vurdert til 5 ut av 5av Simon Bünemann, 2 måneder siden
- Vurdert til 5 ut av 5av ADKFZ8O, 3 måneder siden
- Vurdert til 5 ut av 5av Marw, 3 måneder siden
- Vurdert til 2 ut av 5av Firefox-bruker 15990777, 3 måneder siden
- Vurdert til 5 ut av 5av Arman Daneshjoo, 3 måneder siden
- Vurdert til 5 ut av 5av elmika, 4 måneder siden
- Vurdert til 5 ut av 5av Firefox-bruker 19469020, 4 måneder siden