Beoardielingen foar NoScript Security Suite
NoScript Security Suite troch Giorgio Maone
1.694 beoardielingen
- Wurdearring: 5 fan 5troch Firefox-brûker 14283637, 7 jierren lyn
- Wurdearring: 5 fan 5troch Jimmy Montano, 7 jierren lyn
- Wurdearring: 5 fan 5troch mk_hdh, 7 jierren lyn
- Wurdearring: 5 fan 5troch Paramdeo Singh, 7 jierren lyn
- Wurdearring: 5 fan 5troch 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. - Wurdearring: 5 fan 5troch Firefox-brûker 13849996, 7 jierren lynexcellent script great help. I like it very much. thanks to the developer...
- Wurdearring: 5 fan 5troch Pcamellon, 7 jierren lynI like the customised way of blocking or allowing specific scripts.
- Wurdearring: 5 fan 5troch Firefox-brûker 14265306, 7 jierren lyn
- Wurdearring: 5 fan 5troch Firefox-brûker 13567416, 7 jierren lyn
- Wurdearring: 5 fan 5troch Firefox-brûker 13017503, 7 jierren lyn
- Wurdearring: 5 fan 5troch Firefox-brûker 14254467, 7 jierren lyn
- Wurdearring: 5 fan 5troch Aaaaha, 7 jierren lyn
- Wurdearring: 5 fan 5troch JxReach, 7 jierren lyn
- Wurdearring: 5 fan 5troch Firefox-brûker 12917606, 7 jierren lyn
- Wurdearring: 5 fan 5troch Firefox-brûker 13513522, 7 jierren lyn
- Wurdearring: 5 fan 5troch Andrew, 7 jierren lyn
- Wurdearring: 5 fan 5troch Firefox-brûker 12900474, 7 jierren lynMelhor extensão do Firefox.
Best Firefox add-on. - Wurdearring: 5 fan 5troch Firefox-brûker 14223793, 7 jierren lynYou must trust a domain every time you visit a new site. But after it works fine.