Shqyrtime për NoScript Security Suite
NoScript Security Suite nga Giorgio Maone
Shqyrtim nga 14275679 përdoruesi Firefox-i
Vlerësuar me 5 yje nga 5 të mundshëm
nga 14275679 përdoruesi Firefox-i, 7 vite më parëUPDATE: 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.
2366 shqyrtime
- Vlerësuar me 2 yje nga 5 të mundshëmnga 14558205 përdoruesi Firefox-i, një orë më parëSince the v12.6 update, I am experiencing enormous usability problem. Has the functionality changed in fundamentla way - without communicating ?
After fuzzing around quite a bit, I resolved how to roll-back to the previous version v12.1.1 . Uff, resolved for now.Përgjigje zhvilluesi
postuar më 28 minuta më parëCould you please report at https://noscript.net/forum or https://github.com/hackademix/noscript/issues with some more details to assess the problem?
Thanks! - Vlerësuar me 5 yje nga 5 të mundshëmnga 镂心鉥肝, 14 orë më parëNoScript还是很好的,不管是界面还是解释如何使用都进行了改进。不过,文章内容应该更加简洁一点。告诉用户每一个功能开关的意思。同时NoScript默认会阻止扩展脚本
- Vlerësuar me 4 yje nga 5 të mundshëmnga 17847461 përdoruesi Firefox-i, 2 ditë më parë
- Vlerësuar me 5 yje nga 5 të mundshëmnga 18989716 përdoruesi Firefox-i, 3 ditë më parë
- Vlerësuar me 1 yje nga 5 të mundshëmnga Max, 4 ditë më parëI really wanted to use NoScript. I prefer single-purpose extensions that focus on doing one job well, compared to more multi-purpose extensions like uBlock Origin.
However, I ultimately couldn't stick with it because the user experience did not suit my needs.
E.g. one mobile screen presents around 12 different icons packed into the height of 3 lines of text, leaving a large portion of the screen completely empty below them.
My main frustration is that none of these icons have labels. Expecting users to learn and memorize the meaning of a dozen different unlabeled symbols creates an unnecessary barrier to entry and makes using the extension quickly and efficiently very difficult. It feels counter-intuitive to leave so much screen real estate blank when that space could be used to label each icon and explain its function.
uBlock Origin is easier to use than NoScript. - Vlerësuar me 5 yje nga 5 të mundshëmnga LittleFire, 9 ditë më parë
- Vlerësuar me 5 yje nga 5 të mundshëmnga Absinthe, 10 ditë më parë
- Vlerësuar me 4 yje nga 5 të mundshëmnga thofree, 15 ditë më parëGets 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.
- Vlerësuar me 4 yje nga 5 të mundshëmnga 18920843 përdoruesi Firefox-i, 15 ditë më parë
- Vlerësuar me 5 yje nga 5 të mundshëmnga 18315395 përdoruesi Firefox-i, një muaj më parë
- Vlerësuar me 5 yje nga 5 të mundshëmnga VonD68, një muaj më parë
- Vlerësuar me 5 yje nga 5 të mundshëmnga luis, një muaj më parë
- Vlerësuar me 5 yje nga 5 të mundshëmnga Retromania, një muaj më parë
- Vlerësuar me 5 yje nga 5 të mundshëmnga Luciano Rangel, një muaj më parë
- Vlerësuar me 5 yje nga 5 të mundshëmnga 18924473 përdoruesi Firefox-i, një muaj më parë
- Vlerësuar me 4 yje nga 5 të mundshëmnga arcadia12, një muaj më parëNoscript can't block "redirection ads"
- Vlerësuar me 5 yje nga 5 të mundshëmnga 18903740 përdoruesi Firefox-i, 2 muaj më parë
- Vlerësuar me 5 yje nga 5 të mundshëmnga 15309210 përdoruesi Firefox-i, 2 muaj më parëSimply 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.
- Vlerësuar me 5 yje nga 5 të mundshëmnga FireZilla, 2 muaj më parë
- Vlerësuar me 5 yje nga 5 të mundshëmnga Brutto WP, 2 muaj më parë
- Vlerësuar me 4 yje nga 5 të mundshëmnga Ying Go, 2 muaj më parë