Known sites, permission granted, but javascript not working

[yojimbo]

I'm not sure how to describe this but will try my best.

Something appears to have occurred to my FireFox and NoScript install under Windows 7. Suddenly (or so it appears) sites that I have been visiting for years no longer respond to javascript clicks. This is something I first noticed in the past week, and have spent some time digging under the hood to track down.

The only solution I have found to work reliably is to disable NoScript, a solution I do not find acceptable for obvious reasons!

Security Essentials and MalwareBytes do not indicate anything unwanted in my system. Turning off, even uninstalling, the 5 or 6 other FireFox extensions I use has not made a difference. I even created a new user profile, which seemed to work... for a day. There's been no new hardware, no major software installs.... I've never been quite this clueless how to proceed troubleshooting and solving the problem.

I feel I haven't provided enough useful information, but can anyone give me some advice how to proceed to figure out what's happened? At least, to point me in the right direction.?

[Tom T.]

Suddenly (or so it appears) sites that I have been visiting for years no longer respond to javascript clicks.

What exactly is meant by "javascript clicks"? A JS link, or a click on NS menu to allow/forbid a JS site/source?

I even created a new user profile, which seemed to work... for a day.

Presumably, after doing this (the correct diagnostic action; thanks for doing that), you also re-installed your other add-ons?

Most likely, there's a conflict between NS and one or more of the others.

For the "cleanest" test, please create another new profile from scratch. Install only NoScript.
We'll assume the issue disappears as you test this for a day or whatever.

Now, add back your other add-ons until the symptom reappears. The one that causes the symptom is probably the culprit.
But to be sure, remove all add-ons other than NS. Ensure that everything works properly again.
Then add *only* the one that seemed to cause the issue, as above.
If the two together cause the issue, we've identified the culprit.

If not, it gets a bit more time-consuming, pairing each add-on with NS in your well-functioning profile.
Mozilla suggests trying half of the add-ons. If no problem, try the other half.
Whichever half, then try half of *those*. -- etc. Keeping NS always.

More info in Standard Diagnostic and General Troubleshooting Instructions.