InformAction Forums

I've been holding out and waiting for NoScript to work smoothly with Firefox Sync so I leave noscript.sync.enabled;true foolishly set. Sometimes I find my whitelist is blanked and never find the root cause. However, quite frequently I have to click on allow site once and the site reloads then the exact same root domain allow site popup occurs so I click on allow again and then the site behaves as expected. Sometimes the page will load on the first allow incident and render, but if I click on say a video that would be blocked it wouldn't take the request until I perform the second allow site action.

I'm sure the answer will be just set noscript.sync.enabled;false, but I'm hoping that I've not read something in the forums that resolves this behavior.

For starters, have you read through the thread, "NoScript and Firefox Sync",
-- especially from this post onwards? -- which sounds somewhat similar to your issue.

If you have, and no answer from that, then we'll look elsewhere. Just checking, thanks.

Now that NoScript 3 has been delayed with no new ETA, are there any plans to fix that sync issue in the 2.x line?

Have both of you tried the steps outlined here and here, with a possible typo in the latter, as noted here, and not yet responded to by Giorgio?

It might be better to post further questions and replies in that thread, which Giorgio apparently monitors with some regularity.

Note that the "whitelist erased" issue is addressed there. Thanks for your patience.

Thanks for your reply Tom T. Unfortunately I was too vague in my post, I was actually referring to this issue.

Very delayed reply. I forgot to follow up on this forum post. I think my issue is the behavior of sync settings when modifying the config. I believe from what Giorgio had said is that if one does not modify the noscript.sync.enabled from default to "true" then settings under this chain will not be created: services.sync.prefs.noscript.*

I had toggled noscript.sync.enabled from true to false in response long ago, but recently discovered when adding a new account in FF sync the whitlist was nuked every time. In response I reviseted my config and I just recently toggled "services.sync.prefs.sync.noscript.asyncNetworking" from true to false. Hopefully that stops that erasure of whitelist behavior.