NateofCA wrote:Thanks for fast reply. No I'm not running Firefox sandboxed or virtualized. I don't even know how to set it up to do either of those.
You would need a third-party program to do that. I just had to eliminate the possibility.
Also I don't know whether I have write permissions to prefs.js or not and I don't know where to go change those permissions either. I am admin on this machine
If you are admin, you have the permissions.
I think I might have a clue about what has happened not though. On this machine with the NoScript permission problems I tried to set up Syncing for Firefox so I could sync my bookmarks and add-ins with other machines.
From what I've seen and heard, Sync is a big headache. I've never tried it, and from the sound of it, don't care to.
The thing that tipped me off about that is every time I start Firefox now it wants to check the compatibility of my Add-ons.
That should happen only after Firefox has been updated. When it updates, do you allow it to go to the Mozilla web site (firewall permission, etc.) to confirm the update was successful, etc.? I've found that if you don't, it keeps trying to go there at each start until you finally let it.
Or that too is something else that is not being saved -- the fact that you *did* let the update Welcome (or whatever) screen run. Which would be a Firefox issue, not a NoScript issue. Try a clean profile as previously recommended. It is not unusual for profiles to become corrupt, and perhaps messing with Sync on and off etc. had a hand in that.
By the way; I suspect NoScript will not save permissions for any sites.
Rather than suspect, it's easy enough to test. Go to a new, but presumably trustworthy, site, such as a bank at which you do *not* have an account. Allow their script permanently (whitelist), close the browser, restart, go back to the bank, and see if you're prompted again. Perhaps try this once or twice more at other similar trusted places. Then you know whether it's just certain sites or all sites.