Page 1 of 1

NoScript totally blocks an entire domain that uses JS.

Posted: Sun Jun 12, 2016 8:46 am
by usalabs
OK, so I've been using NoScript for quite a while now, and it helps me with sites that are full with advertisements that use JS, but NoScript has a huge flaw, and that is it WILL block ALL JS on a site that heavily relies on JS even though the domain name is added to NoScipt whitelist, but completely disabling the addon, allows the site to work properly.

One such site is http://splice.com regardless of allowing the domain and then allowing all this page, does nothing, even if initially adding it to NoScript whitelist, the site is still blocked, there has to be a way for NoScript to literally allow an entire domain no matter if it's just one page or several pages, through the blocking, I don't want to keep on going to the firefox addons, disable NoScript, then restarting firefox, just to load splice.com (oh and splice.com is a music collaboration site).

Re: NoScript totally blocks an entire domain that uses JS.

Posted: Sun Jun 12, 2016 9:55 am
by therube
I imagine you're blocking something, elsewhere.

Looks to work here, needing:

+googleadservices.com
+twitter.com
+stripe.com
+splice.com

Re: NoScript totally blocks an entire domain that uses JS.

Posted: Sun Jun 12, 2016 3:08 pm
by barbaz
therube wrote:Looks to work here, needing:

+googleadservices.com
+twitter.com
+stripe.com
All of these domains (that is, these quoted domains) have surrogate script. If it's not working without these Allowed, then we have NoScript bug.

Re: NoScript totally blocks an entire domain that uses JS.

Posted: Mon Jun 13, 2016 3:42 am
by Thrawn
usalabs wrote:allowing the domain and then allowing all this page, does nothing
Bear in mind that when you allow JavaScript to run, it may try to load scripts from new domains, which weren't previously attempted and therefore didn't show up in the menu - so they'll still be blocked. 'Allow all this page' really means 'Allow all currently visible on the menu'. So you might need to use it multiple times before the scripts have finished loading scripts that load scripts that load scripts that load scripts...it's not terribly efficient, and it certainly isn't NoScript's fault that pages are designed this way, but it's reality. If you really want control over all those mashed-up scripts, then having to 'allow all' multiple times is a small price to pay.