by libove » Fri Oct 20, 2017 6:58 am
I see that this has been discussed a few times over history. None of the threads that I found about this seem to describe what I'm seeing. (Perhaps more correct to say, the proposed fixes don't seem to apply).
Firefox 56.0.1 64-bit on Windows 10 Enterprise.
Windows Domain connected machine, logged in to a Windows Domain user account.
NoScript currently at 5.1.3rc2. (I see that there has been a quick series of RC releases of NoScript recently. This has been going on for days at least, maybe weeks).
[ Not sure if I've noticed it on my other three computers, or just this one that I use the most. I think I have noticed it on others too ]
Basically, I access a site that I am absolutely certain I have whitelisted, and NoScript is blocking it again, as though my past whitelist action for the site has been forgotten.
Seems like there should be a FAQ for this problem. (Is there a FAQ for this problem? I don't see one in the NoScript FAQ)
So, how to diagnose what's going on here, and correct it?
thanks,
Jay
I see that this has been discussed a few times over history. None of the threads that I found about this seem to describe what I'm seeing. (Perhaps more correct to say, the proposed fixes don't seem to apply).
Firefox 56.0.1 64-bit on Windows 10 Enterprise.
Windows Domain connected machine, logged in to a Windows Domain user account.
NoScript currently at 5.1.3rc2. (I see that there has been a quick series of RC releases of NoScript recently. This has been going on for days at least, maybe weeks).
[ Not sure if I've noticed it on my other three computers, or just this one that I use the most. I think I have noticed it on others too ]
Basically, I access a site that I am absolutely certain I have whitelisted, and NoScript is blocking it again, as though my past whitelist action for the site has been forgotten.
Seems like there should be a FAQ for this problem. (Is there a FAQ for this problem? I don't see one in the NoScript FAQ)
So, how to diagnose what's going on here, and correct it?
thanks,
Jay