InformAction Forums

Seems like someone else has this same problem.

When scripts in Default are not allowed, then Firefox acts like every script is blocked on every site.

In Trusted everything is allowed, In custom too (no pages are customised though.)
Making every link trusted does nothing. And http-unlock either.
Only if I allow scripts in Default or in Options page globally then the sites are working "normally".
The capchtas here are working because I've allowed scripts globally.

PS. I use Windows 7 32 bit Home premium; on my other computer with Win 7 32 professional, nosript seems to work somehow, but I haven't had time to explore how properly.)

Did you use a http website? If so, when switching to Trusted change the padlock from green to red and reload the page which allows http + https content to load. It should then work as usual and allow scripts etc. This is crucial because if you don't do this, settings for http websites will be ignored because NS thinks you've restricted your approvals to https URLs only.

When switching from Trusted to Custom, the latter will apply the checkboxes from Trusted (which is also true for Default) that's why you saw ticked (and for Default untickted) checkboxes although you never really customized these settings yourself.

Quest wrote:Seems like someone else has this same problem.

When scripts in Default are not allowed, then Firefox acts like every script is blocked on every site.

In Trusted everything is allowed, In custom too (no pages are customised though.)
Making every link trusted does nothing. And http-unlock either.
Only if I allow scripts in Default or in Options page globally then the sites are working "normally".
The capchtas here are working because I've allowed scripts globally.

PS. I use Windows 7 32 bit Home premium; on my other computer with Win 7 32 professional, nosript seems to work somehow, but I haven't had time to explore how properly.)

If it isn't the http/https issue (which I think the "And http-unlock either" means),

So that "having a domain set to trusted with all check-marks set" means it suppresses scripts,
but changing the default means all site in default properly execute scripts.

try going to the options, enabling the debug stream at the bottom, and check whether the capabilities under the "trusted" look like this

"TRUSTED": {
"capabilities": [
"script",
"object",
"media",
"frame",
"font",
"webgl",
"fetch",
"other"
]