- von JustHereForTheReviews, vor 10 TagenBewertet mit 1 von 5 SternenI WOULD give it 5 stars... but when it comes to online shopping experiences that use some sort of 3rd-party point-of-sale (POS) facilitator agent, NoScript FAILS to account for it in ANY capacity. This has been a persistent problem for YEARS.
I get it: You have to whitelist someone. Well, businesses are not under any sort of regulation to tell you who handles their transactions, so unless you know who to whitelist, what do you do?
First the vendor thinks your bank blocked them, then you lower NoScript.
Then, your bank thinks the second time is a double-charge, so they block it. You have to call your bank and authorize.
Then, the third time, the VENDOR may try to audit you!!
This is NOT acceptable. NoScript is an EXCELLENT blocker... but the problem is that it's TOO POWERFUL to be practical at all.
Antwort des Entwicklersgeschrieben am vor 10 TagenI'm sorry to hear about your bad experience.
Could you please report at https://noscript.net/forum providing some real world examples of this?
One approach that can anyway work-around this issue would be using the "Disable restrictions for this tab" button just before initiating the transaction which would potentially send you to a 3rd party POS.
Millions of NoScript users (including myself) do e-shopping everyday, and such incidents (double billing or blocking) because of scripts not being initially enabled on the payment processors page have not been reported, at least not recently.
It used to be an issue with the XSS filter, but not anymore since its design has been changed (many years ago) providing "in flight" UI to decide whether allow or block the suspicious request.
Furthermore, many payment processors come preset to TRUSTED in the built-in configuration "just in case", so your report may be useful to update this list. Thanks.
- von Firefox-Benutzer 16255010, vor 13 TagenBewertet mit 1 von 5 SternenI had to disable it.
Besides the latest version of Firefox, I still have a portable Firefox 29.0.1 on my PC, with a NoScript 188.8.131.52 .
That version allowed to PERMANENTLY allow everything on a web site. This version doesn't, and I have to reallow all on web sites on each Firefox restart.
This is far too tedious and problematic.
Why the author needed to ruin a good thing is known only to himself...
- von Firefox-Benutzer 16453607, vor 7 MonatenBewertet mit 1 von 5 SternenNoScript does what it says it does - in that respect it's ok. As popular as NoScript isn the problem is when you visit a website it blocks a bunch of scripts by default without identifying "which" script is responsible for the web page element making it difficult to navigate the site. It is not useful to simply list blocked scripts without knowing what each is responsible for. Main issue is most users do not know which specific scripts from a list to enable, or leave disabled, in order to navigate the scripts as required. If users have to enable all scripts then that's like not having NoScripts turned on. If users have to disable all (non-default) scripts then browsing is virtually impossible. What is needed is a NoScript icon over each area on visited web pages to notify users what is blocked and what isn't - at least that way users can select on a need basis what to enable or leave disabled.