Page 1 of 1

noscript blocking a website while scripts enabled

Posted: Tue Jun 21, 2011 12:00 pm
by RedDwarf
It appears that noscript is blocking a website while scripts are allowed globally. I noticed it on the following site, the javascript in the Features/Benefits section does nothing while noscript is enabled but functions as soon as I disable the noscript extension.

http://www.scan.co.uk/products/akasa-ak ... d-1-int%29

I have the latest version, 2.1.1.1 installed and I was using an earlier version with the same result.

Why is it doing this?

Re: noscript blocking a website while scripts enabled

Posted: Tue Jun 21, 2011 12:28 pm
by dhouwn
Going on the site, having "www.scan.co.uk" (and some others like "yimg.com", "yahoo.com", "googleapis.com" and "facebook.com", but I guess these don't play a role) allowed it works for me, so in the opt-in mode the site can be made working.

Without allowing "www.scan.co.uk", it does not work. Seems to me like the "attempt to fix JavaScript links" feature could be improved for these kinds of sites.

Re: noscript blocking a website while scripts enabled

Posted: Tue Jun 21, 2011 2:12 pm
by therube
Appears all that is needed is scan.co.uk & googleapis.com.
(googleapis.com being quite commonly needed these days.)
Maybe you are blocking googleapis.com in AdblockPlus or the like?

Re: noscript blocking a website while scripts enabled

Posted: Wed Jun 22, 2011 1:02 am
by RedDwarf
therube wrote:Appears all that is needed is scan.co.uk & googleapis.com.
(googleapis.com being quite commonly needed these days.)
Maybe you are blocking googleapis.com in AdblockPlus or the like?
I only have noscript running on this Firefox browser and I had disabled everything that could affect javascript.

The strange thing is, earlier when I tried it it would not work unless I disabled noscript extension but now it is working for some reason.

I have tried forbidding the needed sites such as scan and googleapi and all of them and then allow globally but now it works whereas earlier it did not.

Something like this has happened before and I could not explain why at one time it wasn't working and at another it was. That was a problem with requestpolicy which I don't run on this browser profile.

If it re-occurs I will update this thread.