NoScript causing Firefox problems

[GreenGreat]

We have now removed NoScript from my current Firefox as it was causing too many problems. Not lots, just important ones.

NoScript has served me well for a number of years. Now it keep causing problems even when turned off. I have had to remove it. My operating system is Windows 7 and Firefox is up to date. This has been creeping up for a few months. Is anyone else having this problem? It seems to work OK at present on my laptop which is also Windows 7.

The last straw was when it stopped me paying my energy bills on line ... the message began "Java.lang. NullPointerException "

Recently it has stopped Firefox displaying Facebook. This has crept up gradually, first I had to keep reloading, then nothing would make it display ... other than disabling (not just allowing Global) NoScript.

This problem doesn't affect my other browsers, and oddly doesn't affect my laptop, which is basically the same setup as my desktop. But I use the desktop for more routine things. I have noticed that more and more I have to "allow Global" for processes not to be interrupted.

Does anyone else have the same problem? I realise it could be my system, but we have looked at a lot of things.

[Thrawn]

Now it keep causing problems even when turned off.

If, by "turned off", you mean that the addon is disabled, then the problems you're experiencing are not related to NoScript.

The last straw was when it stopped me paying my energy bills on line ... the message began "Java.lang. NullPointerException "

I recognise that message - I'm a Java programmer by trade - and it is completely unrelated to NoScript. It's something wrong at the server, not in the browser.

Recently it has stopped Firefox displaying Facebook. This has crept up gradually, first I had to keep reloading, then nothing would make it display ... other than disabling (not just allowing Global) NoScript.

That's something we can at least investigate. Can you look in the Browser Console (Ctrl+Shift+J) when it occurs, and see whether any NoScript-related messages appear (ignoring CSS messages).

I have noticed that more and more I have to "allow Global" for processes not to be interrupted.

If global allow makes a difference, then it should be possible to resolve issues by whitelisting specific sites.

Does anyone else have the same problem? I realise it could be my system, but we have looked at a lot of things.

It depends on exactly what the problem is, but I don't have trouble with Facebook.

[barbaz]

This problem [...] oddly doesn't affect my laptop, which is basically the same setup as my desktop.

The obvious thing to try would be to create a new profile on the desktop computer, then completely shut down Firefox on both machines, then copy the entire contents of your laptop profile into the newly created profile on the desktop computer, overwriting anything that is already there.
Does that produce a working setup on your desktop?

[GreenGreat]

Thank you both for your input. I am not technical and don't want to investigate without someone who is, but I can get help from a more savvy friend over the weekend to look at this and try and resolve it.

No, by switched off I just meant, Global allow.

[GreenGreat]

Now it keep causing problems even when turned off.

I recognise that message - I'm a Java programmer by trade - and it is completely unrelated to NoScript. It's something wrong at the server, not in the browser.

Thank you that is useful. Thing is that I tried it twice with NoScript running, and this message came up. Then removed NS, and the site worked, so I had to draw a conclusion that NS was involved.

[Thrawn]

No, by switched off I just meant, Global allow.

Ah, that's different. NoScript does a lot more than just blocking JavaScript, so globally allowing scripts is not the same thing as turning it off.

Can you look in the Browser Console for NoScript-related messages when there are problems?

[barbaz]

@Janet: your post is at viewtopic.php?f=7&t=21150