Hi,
I have NoScript 2.2.4 in Seamonkey 2.0.14. I'm no longer using Seamonkey due to vulnerabilities.
I am currently using Pale Moon 9.2 (comparable to Firefox 10).
Can I export all of my settings from Seamonkey's NoScript (using the bottom export button in the NoScripts Options) and import them into a new NoScript that I plan to install in Pale Moon? Or, if I can't transfer all of my settings, can I export my Whitelist from the old Seamonkey to Pale Moon? I know the version of NoScript will be a newer version than what is in Seamonkey.
I appreciate any advice.
Sincerely, Libra
Can ITransfer my NS settings to a different browser
Can ITransfer my NS settings to a different browser
Mozilla/5.0 (Windows NT 6.0; rv:9.2) Gecko/20120218 Firefox/9.2 PaleMoon/9.2
Re: Can ITransfer my NS settings to a different browser
First, please note that NoScript developer Giorgio Maone tells us that while NoScript *might* work on other Gecko-based forks, compatibility and support are assured only for Firefox and Seamonkey. Please consider that.
In a thread on another topic, a user reported that a particular error did not occur on 64-bit Fx, but occurred on 64-bit Pale Moon and Waterfox. So there is real-world evidence that you may experience problems with NoScript on other than SM and FF.
I don't know of any reason why the import/export buttons wouldn't work, assuming that the alternate browsers use the prefs.js file to store configurations in the same way, but that's not a guarantee. If you still want to do this, give it a try, and let us know.
Curious: Which unpatched vulns in SM?
Do they exist in Firefox also?
And Pale Moon patched them, but Mozilla did not? ... not doubting you, but would certainly like to know.
Cheers.
In a thread on another topic, a user reported that a particular error did not occur on 64-bit Fx, but occurred on 64-bit Pale Moon and Waterfox. So there is real-world evidence that you may experience problems with NoScript on other than SM and FF.
I don't know of any reason why the import/export buttons wouldn't work, assuming that the alternate browsers use the prefs.js file to store configurations in the same way, but that's not a guarantee. If you still want to do this, give it a try, and let us know.
Curious: Which unpatched vulns in SM?
Do they exist in Firefox also?
And Pale Moon patched them, but Mozilla did not? ... not doubting you, but would certainly like to know.
Cheers.
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.27) Gecko/20120216 Firefox/3.6.27