InformAction Forums

I just ran Firefox for the first time in 6-7 hours. I noticed no website had working Javascript, and then realized by opening NS settings that the only customized websites were those that come by default.

I had been customising these settings again since the quantum version, and now I have to do it all over Seriously this is too disappointing.

If you need more feedback I can not say what has happened since. The PC went in suspend mode but Firefox has been closed since then. Did 10.1.6.3 get pushed today/yesterday?

NoScript allows you to backup (and restore, of course) your settings:

NNSU wrote:I just ran Firefox for the first time in 6-7 hours. I noticed no website had working Javascript, and then realized by opening NS settings that the only customized websites were those that come by default.

Either you permitted all the others by setting them to "Temporary TRUSTED", or something happen to your profile which deleted the WebExtensions storage area reserved to NoScript.
No way NoScript lose its setting by itself alone, anyway.
As FranL suggested, though, since stuff like that may happen for any data storage, making periodic backups is a good idea.

There have been multiple reports on this issue but no one can reproduce it yet. It seems to happen at random.

Losing all your customized settings after investing time in configuring them can be really frustrating. If your settings were reset after Firefox was closed or the PC went into suspend mode, it could be due to a profile corruption, an update, or an issue with how preferences are stored. Checking about:profiles might help determine if Firefox created a new profile and if your previous settings are still available. If an update caused the reset, reviewing recent changelogs or community discussions could provide insights. For users who rely on stable browser configurations, especially in custom website development, unexpected resets can disrupt workflows. Restoring a backup of your Firefox profile, if available, or enabling a settings sync feature could help prevent this issue in the future.

tonni wrote: ↑Wed Feb 12, 2025 12:35 pm enabling a settings sync feature could help prevent this issue in the future.

Oh dear, what a reckless suggestion. If you're going to try to help people, please first actually know what you're talking about.

Enabling Sync is known to CAUSE the same outcome as this issue for some people.

And a NoScript 10.1.6.3 update issue surely does not have any current relevance, so in any case there is no point continuing this thread anymore. Locking.