Vurdering for NoScript Security Suite
NoScript Security Suite av Giorgio Maone
Vurdering av Firefox user 14275679
Vurdering: 5 av 5
av Firefox user 14275679, 7 år sidanUPDATE: 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 388 vurderingar
- Vurdering: 3 av 5av Air, 12 dagar sidanVery useful on a computer, however, enabling it by default on a mobile phone will block many important features, including but not limited to any AI features and video browsing
- Vurdering: 2 av 5av Firefox user 19157064, 19 dagar sidanCompletely breaks reddit on mobile, site becomes unusable. I only got it for help blocking reddits creepy tracking bs on this browser.
- Vurdering: 1 av 5av Cory Sanin, 19 dagar sidanOne star for SidebarUtil.tab.js
Disruptive as hell and for what? Why do you need to know if I have a sidebar open? I don't even know what a sidebar is. Remove this nonsense. - Vurdering: 5 av 5av Firefox user 19145735, 20 dagar sidan
- Vurdering: 5 av 5av And?, 24 dagar sidan
- Vurdering: 5 av 5av A Tea Daze, 25 dagar sidan
- Vurdering: 5 av 5av srzlt, ein månad sidan
- Vurdering: 5 av 5av jordan9543, ein månad sidan
- Vurdering: 5 av 5av vit55555, ein månad sidan
- Vurdering: 5 av 5av Firefox user 18218075, ein månad sidan
- Vurdering: 5 av 5av fiendkaka, ein månad sidan
- Vurdering: 5 av 5av Shannon Sobeck, ein månad sidan
- Vurdering: 5 av 5av Flyyyyyyyyyyyyyyyy, ein månad sidan
- Vurdering: 5 av 5av Firefox user 19088604, ein månad sidan
- Vurdering: 5 av 5av kk, ein månad sidan
- Vurdering: 5 av 5av Firefox user 19072892, 2 månader sidan
- Vurdering: 5 av 5av cwqing1973, 2 månader sidan
- Vurdering: 5 av 5av Firefox user 14468519, 2 månader sidan
- Vurdering: 5 av 5av rabbitshee, 2 månader sidan
- Vurdering: 5 av 5av Firefox user 19047433, 2 månader sidan
- Vurdering: 5 av 5av A. Bilmanda, 2 månader sidan
- Vurdering: 5 av 5av Lazer Bear, 2 månader sidan