Bewertungen für NoScript
NoScript von Giorgio Maone
2.373 Bewertungen
- Bewertet mit 5 von 5 Sternenvon Jimmy Montano, vor 7 Jahren
- Bewertet mit 5 von 5 Sternenvon mk_hdh, vor 7 Jahren
- Bewertet mit 4 von 5 Sternenvon Vit, vor 7 JahrenI like it but my rules were reset a few times.
p.s. is there a list of privileged pages?Antwort des Entwicklers
geschrieben am vor 7 JahrenThe "privileged pages" are those which WebExtensions cannot have access to, i.e. a bunch of about:xyz pages, plus the domains listed in this about:config preference:
extensions.webextensions.restrictedDomains
Anyway using this as a discussion forum is not a good idea. Please report your reset issue (and bring other discussions, if any) at https://noscript.net/forum, thank you! - Bewertet mit 4 von 5 Sternenvon Nefae, vor 7 Jahren
- Bewertet mit 4 von 5 Sternenvon MuhoRog, vor 7 JahrenIn the Livejournal when the noscript is enabled, player youtube is not available. It's just not there. His noscript cuts out. Please fix it. This has been happening for a long time. But you can not fix it. When I turn off the noscript, everything becomes correct. Sorry for my English.
- Bewertet mit 5 von 5 Sternenvon Paramdeo Singh, vor 7 Jahren
- Bewertet mit 5 von 5 Sternenvon Firefox-Benutzer 14275679, vor 7 JahrenUPDATE: 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. - Bewertet mit 3 von 5 Sternenvon 果駱客, vor 7 Jahrennot as good as it used to be, 為何"信任這個網頁所有物件"要拿掉 ?@@
- Bewertet mit 5 von 5 Sternenvon Firefox-Benutzer 13849996, vor 7 Jahrenexcellent script great help. I like it very much. thanks to the developer...
- Bewertet mit 5 von 5 Sternenvon Pcamellon, vor 7 JahrenI like the customised way of blocking or allowing specific scripts.
- Bewertet mit 5 von 5 Sternenvon Firefox-Benutzer 14265306, vor 7 Jahren
- Bewertet mit 5 von 5 Sternenvon Firefox-Benutzer 13567416, vor 7 Jahren
- Bewertet mit 5 von 5 Sternenvon Firefox-Benutzer 13017503, vor 7 Jahren
- Bewertet mit 5 von 5 Sternenvon Firefox-Benutzer 14254467, vor 7 Jahren
- Bewertet mit 5 von 5 Sternenvon Aaaaha, vor 7 Jahren
- Bewertet mit 5 von 5 Sternenvon JxReach, vor 7 Jahren
- Bewertet mit 5 von 5 Sternenvon Firefox-Benutzer 12917606, vor 7 Jahren
- Bewertet mit 4 von 5 Sternenvon Firefox-Benutzer 13996824, vor 7 JahrenWelp, it works.The only drawback is that setup menu has realy non-intuitive icons.
- Bewertet mit 3 von 5 Sternenvon fluks, vor 7 Jahren
- Bewertet mit 4 von 5 Sternenvon Firefox-Benutzer 14244150, vor 7 Jahren
- Bewertet mit 5 von 5 Sternenvon Firefox-Benutzer 14242035, vor 7 JahrenFF 61.0.2, extention dont work(
- Bewertet mit 4 von 5 Sternenvon Firefox-Benutzer 14240897, vor 7 JahrenA must have Extension!
However I can confirm the problems with "disable restrictions for this tab"
It started with version 10.1.8.17
Whenever restrictions are disabled the site will not load correctly and Firefox will become stuck in a loading loop.
This will also result in high cpu load.
Mainly FirefoxCP Web Content + WebExtensions
I also use an additional ad blocker (ghostery) but disabling it won't change anything.
10.1.8.20 no joy
Only solution so far... reverting back to .16 - Bewertet mit 5 von 5 Sternenvon Firefox-Benutzer 13513522, vor 7 Jahren