Отзывы на NoScript
NoScript от Giorgio Maone
Отзывы Пользователь Firefox 13551289
Оценено на 2 из 5
от Пользователь Firefox 13551289, 8 лет назадOk, I just got the update and have to say I really hate the new version and am considering dumping it completely. There are a lot of reasons why.
Under the old version, when you visit a new website, it shows a popup saying that scripts are disabled and giving you a quick option to temporarily or permanently enable scripts for just that website. Under the new version, you don't even know if the scripts are blocked, and if the website is malfunctioning because it needs its scripts, or what.
Also, the new UI really sucks. Everything is all icons now and I don't have a clue what any of them do. Am I allowing scripts or blocking them? Am I permanently allowing them or just temporarily? You could at least give us the option to go back to the classic interface.
I've also noticed that for every single website I go to, I have to tell it not to allow XSS from that website to facebook.com. It's really annoying. There is no option to just say, don't allow XSS from anywhere to facebook.com. Under the old version, it only gave me an XSS warning for a certain few websites which I could then do an unsafe reload. Now it's like there's cross-scripts everywhere.
Ok so maybe a useful feature would be to allow for example facebook.com (seems to be the main offender here) when I'm ON facebook.com, but disable it when any other website tries to cross-script to it.
Anyway to sum it up, the new version nags me incessantly and isn't clear enough about what's going on for me to figure out how to allow the scripts I want and block the ones I don't. Please go back to the old version.
Under the old version, when you visit a new website, it shows a popup saying that scripts are disabled and giving you a quick option to temporarily or permanently enable scripts for just that website. Under the new version, you don't even know if the scripts are blocked, and if the website is malfunctioning because it needs its scripts, or what.
Also, the new UI really sucks. Everything is all icons now and I don't have a clue what any of them do. Am I allowing scripts or blocking them? Am I permanently allowing them or just temporarily? You could at least give us the option to go back to the classic interface.
I've also noticed that for every single website I go to, I have to tell it not to allow XSS from that website to facebook.com. It's really annoying. There is no option to just say, don't allow XSS from anywhere to facebook.com. Under the old version, it only gave me an XSS warning for a certain few websites which I could then do an unsafe reload. Now it's like there's cross-scripts everywhere.
Ok so maybe a useful feature would be to allow for example facebook.com (seems to be the main offender here) when I'm ON facebook.com, but disable it when any other website tries to cross-script to it.
Anyway to sum it up, the new version nags me incessantly and isn't clear enough about what's going on for me to figure out how to allow the scripts I want and block the ones I don't. Please go back to the old version.
Ответ разработчика
размещено 8 лет назад1) The UI shows you all the domains that are trying to run active content, just like before, but more compact. You can allow them individually (by assigning the TRUSTED preset), leave them not running (DEFAULT), blacklisting (UNTRUSTED) or even assign CUSTOM permissions. Not just that, but better than before if you can modify each preset on the fly and even see the minimum permissions needed for the site to work (they've got a pink background).
2) To assign the TRUSTED preset temporarily, you just click it once. To make it permanent, you click the clock icon and make it fade away (temporary->permanent).
3) The XSS filter now has a "Always block requests from a.com to b.com" option, that you can use exactly the way you say you want.
2) To assign the TRUSTED preset temporarily, you just click it once. To make it permanent, you click the clock icon and make it fade away (temporary->permanent).
3) The XSS filter now has a "Always block requests from a.com to b.com" option, that you can use exactly the way you say you want.
2 417 отзывов
- Оценено на 5 из 5от Пользователь Firefox 19487299, 17 часов назад
- Оценено на 5 из 5от Ryan Steed, 10 дней назад
- Оценено на 2 из 5от Wewe Never, 11 дней назадIt doesnt remember changed levels, and 90% of all sites i visit needs permission. Javascript is everywhere I guess. Deleted the addon.
Ответ разработчика
размещено 11 дней назадIf you flag sites as TRUSTED rather than Temp. TRUSTED, permissions are remembered. Otherwise it's a bug, probably with your browser configuration, and should reported at github.com/hackademix/noscript/issues thanks. - Оценено на 5 из 5от ZeroUnderscoreOu, 21 день назад
- Оценено на 5 из 5от 鼎针皮艺, месяц назад
- Оценено на 5 из 5от Bob, месяц назад
- Оценено на 1 из 5от mlatpren, месяц назадIt does a great job at blocking, but is regularly frustrating with re-enabling things. It's supposed to show you what it's blocking, but that's extremely hit-or-miss. Occasionally, there'd be something blocked where the only solution is to disable the extension. As in, right-click and disable *from Firefox itself.*
- Оценено на 3 из 5от zekromVale, месяц назадThere needs to be a CPU limit on this extension, using 30% CPU of an intel i7 11th gen laptop CPU on YouTube is ridiculous. Firefox for Ubuntu snap, flatpack, or just .deb are affected. Must disable NoScript to fix it or allow everything fully for all domains on the page. I would like more domains to be added to the global trusted list though (by default) or have a popup at the top when you first visit a page.
- Оценено на 5 из 5от Hopeavirta, 2 месяца назад
- Оценено на 5 из 5от Lazy Cat, 2 месяца назад
- Оценено на 5 из 5от sumobunny, 2 месяца назад
- Оценено на 5 из 5от Zelgadis-San, 2 месяца назад
- Оценено на 5 из 5от Dadou, 2 месяца назад
- Оценено на 3 из 5от aq, 2 месяца назадUser for at least 15 years, Something is conflicting on Firefox. It is blocking scripts and other add ons such as tampermonkey or violentmonkey with scripts added, but without any listing of what is being blocked. Only option is to shut it off to proceed.
Even blocking games internal scripts without any 'monkey' in use.
Please check and test - Оценено на 5 из 5от Simon Bünemann, 2 месяца назад
- Оценено на 5 из 5от ADKFZ8O, 2 месяца назад
- Оценено на 5 из 5от Marw, 2 месяца назад
- Оценено на 1 из 5от aedgsegsfvw, 3 месяца назадWARNING! Causes crashes with SEVERE data loss. Since mid 2025, this extension regularly causes the browser to crash. It can even crash the browser so severely that windows freezes irreversibly, with SEVERE data loss as a result. The crashes stopped when I deleted this extension, and re-occurred after reinstalling it. Several others have reported the same issues on user forums.
- Оценено на 2 из 5от Пользователь Firefox 15990777, 3 месяца назад
- Оценено на 5 из 5от Arman Daneshjoo, 3 месяца назад
- Оценено на 5 из 5от elmika, 3 месяца назад
- Оценено на 5 из 5от Пользователь Firefox 19469020, 4 месяца назад
- Оценено на 5 из 5от Пользователь Firefox 14500718, 4 месяца назад
- Оценено на 5 из 5от Пользователь Firefox 19459487, 4 месяца назадI'm notified every time WebGL is blocked on each page load. There's no way to disable these notifications and it's very irritating.
Edit: updated to 5 stars as it can be disabled after all but the setting isn't described very clearly.Ответ разработчика
размещено 4 месяца назадYou should not get any notification. Just a little placeholder inside the page, to be able to enable it back. And you can disable it by unchecking "NoScript Options>Appearance>Show synthetic placeholders for invisible capability probes"