InformAction Forums

I have the same problem, and the answer in the FAQ about how to change my settings: Yes, you can, just toggle the Noscript Options|Notifications|XSS preference. ...doesn't apply to the new interface in 10.1.2, as that menu doesn't appear to exist. My only choices in the new interface are to either ...

Hi, I've been using the new noscript v10 and I noticed a lot of websites URLs are truncated at the beginning so I would see things like ...somesite.com where as before I would see the entire url this is frustrating on sites that have something like subdomain.somesite.com because it shows up still a...

Edit: I just reviewed the debug code and figured out that under Untrusted, script, fetch, objects etc. was listed (even though nothing was ticked in the WE). Deleting those entries manually did help as it looks like and now only shows "capabilities": []. However, before I deleted just the...

Or, you can just click on the default button for any source that applies to and remove the checkmarks. The three presets (default trusted and untrusted) can be changed on any of those buttons in the interface for all members of the preset at the same time. I dont get what you mean by that Pansa? Wh...

OK something must have gone wrong when NoScript upgraded. Thanks for your advice everyone, here is how to fix it if someone else has this exact problem: Under the options page -> Debug (very bottom of the page) Once you tick debug, a box of script will open up below. In my failed case it read: So i...

When I manually set the option to allow content from a site that is not using HTTPS, the lock symbol turns green. When I check the list again, my change has been reverted to Default. Presumably because it will not allow content from this site anyway (no HTTPS). * When I use "Temporarily allow ...

At the moment, for me personally, Untrusted never seems to have any effect whatsoever. Despite none of the checkboxes under that option are ticked, the site will load everything regardless. This is odd because in the older version, it would show some html text and no content. have you made the untr...

I'm no programmer but wouldn't it be possible to just tell NS which option and specific settings is used right now? Custom--> look up checkmarks there Default-->lookup checkmarks there without having these two "cross-talking" to each other? It does exactly that for the true presets. But t...

zettos wrote:clarification - constant pop-ups about "cross-site suspicious requests". it's always from "[] to some website"

That's the firefox hub page calling your previously visited pages.

The page that opens in a new tab.

I would like to say just by doing clicking on the lock or unlock, respectively makes NoScript "forget" whether it is trusted. For example, when I navigated to "http://nashvillepublicradio.org", I clicked the trusted for nashvillepublicradio.org , and the unlock button. NoScript ...

I'm not sure what you guys were thinking. NoScript is the total bomb and it has kept me safe and warm for years. I LOVE noscript. That being said this new interface for the new version of Firefox is so obtuse its almost broken. Did any of you actually try surfing about and using it before the relea...

Well, given the fact that the new version of NoScript completely lost my carefully tuned settings since many years back, and noone apparently cares, I'm jumping ship to uMatrix which I've used in other places and like very much as well. This was, sad to say it, a prime example of fixing something t...

I believe the issue is with the Custom tab since it seems to affect Trusted (at least in the older 10.1.1 version) and vice versa. Did you use the latest 10.1.2 update and/or did you use Custom in the first place? Because in its newest release, Trusted (and also Default) seems to overwrite all Cust...

Thanks. I closed all tabs, then turned off all content on "New Blank Page". Then clicked the Add-Ons icon - and the popup arrived! Hopefully it's just leftovers from Firefox shutting things down (I haven't been able to close it yet without getting the Firefox crash detector, so who knows ...