Pógódnośenja za NoScript Security Suite
NoScript Security Suite wót Giorgio Maone
Pógódnośenja wót Wužywaŕ Firefox 14275679
Z 5 z 5 pógódnośony
wót Wužywaŕ Firefox 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.360 pógódnośenjow
- Z 4 z 5 pógódnośonywót thofree, 12 oeren lynGets detected by Youtube's anti ad-block stuff. Wish you had a button to turn it off easily for a website without disabling it entirely.
- Z 4 z 5 pógódnośonywót Wužywaŕ Firefox 18920843, ien dei lyn
- Z 5 z 5 pógódnośonywót Wužywaŕ Firefox 18315395, 12 dagen lyn
- Z 5 z 5 pógódnośonywót VonD68, 13 dagen lyn
- Z 5 z 5 pógódnośonywót luis, 15 dagen lyn
- Z 5 z 5 pógódnośonywót Retromania, 21 dagen lyn
- Z 5 z 5 pógódnośonywót Luciano Rangel, 22 dagen lyn
- Z 5 z 5 pógódnośonywót Wužywaŕ Firefox 18924473, 25 dagen lyn
- Z 5 z 5 pógódnośonywót Wužywaŕ Firefox 18903740, ien moanne lyn
- Z 5 z 5 pógódnośonywót Wužywaŕ Firefox 15309210, ien moanne lynSimply top. I've been using the extension for years and I'm still delighted with it. I can control exactly which website is allowed to do what.
- Z 5 z 5 pógódnośonywót FireZilla, ien moanne lyn
- Z 5 z 5 pógódnośonywót Brutto WP, ien moanne lyn
- Z 4 z 5 pógódnośonywót Ying Go, ien moanne lyn
- Z 5 z 5 pógódnośonywót Wužywaŕ Firefox 9771322, 2 moannen lynУ кого отключились дополнения обновите Firefox до 136 версии.
_____________________
For those who have been disabled add-ons, update Firefox to version 136. - Z 5 z 5 pógódnośonywót GothGlamPrincess, 2 moannen lyn
- Z 5 z 5 pógódnośonywót test, 2 moannen lyn
- Z 5 z 5 pógódnośonywót Spamzilla, 2 moannen lyn
- Z 5 z 5 pógódnośonywót zsyzsykk, 2 moannen lyn
- Z 5 z 5 pógódnośonywót Dulak, 2 moannen lynReally nice, works great, only thing I noticed is that there a weird thing with Alternate Player for Twitch.tv addon.
There seems to be script there that handles the follow button (and clicking that annoying wiggle box at the bottom) and it is getting blocked by noscript, even though it says it's a tab with higher privileges. I have to allow all in tab because the blocked script is not showing up, so i cannot set it to be allowed permanently. - Z 5 z 5 pógódnośonywót Wužywaŕ Firefox 13759941, 2 moannen lyn
- Z 5 z 5 pógódnośonywót catherine martin, 2 moannen lyn