InformAction Forums

Gizmodo, lifehacker and all their sistersites are still having some trouble with Noscript, even if all their domains are on the whitelist and Facebook is on the whitelist too.

It's very odd, as sometimes Noscript will complain, sometimes it will not, about an XSS attack that was blocked from domain [api.facebook.com]


Just mentioning this here, I find it very strange because when it will happen and when it won't happen is completely random to my experience.

No randomness involved in here, when it happens again, please post the output of "Tools → Error Console → Messages", so we might explain to you why the XSS filter was triggered.

Hi,

I can second the problems mentioned in the first post, at least with the lifehacker.com site.
Configuration: WinVista 64, FF3.5.2; NS1.9.7.9.
"lifehacker.com" is in NS's whitelist.
"Temporarily allow current top-level-site" in the General tab is deactivated.

However, when loading http://lifehacker.com and loading one of the blog entries afterwards, the bottom most part of the website shows
"Loading comments ...
In order to view comments on lifehacker.com you need to enable JavaScript.
If you are using Firefox and NoScript addon, please mark lifehacker.com as trusted. "

When clicking on NS's tray icon, the option "temporarily allow http://lifehacker.com" is available. Additionally, the option "forbid lifehacker.com" (without http://) is available.

Tools -- Error Console -- Messages shows two messages, but not related to lifehacker.com (I have several tabs open).

Just forbid lifehacker.com then reallow it.

That worked, thank you.