InformAction Forums

Or does it not matter?

NoScript 10 is not compatible with Firefox < 57. So you have to upgrade to FF 57 first, then get NoScript 10.

Personally I would suggest you hold off on that upgrade a bit longer. Or perhaps test drive it in a Firefox Portable before deciding about upgrading your main Firefox. NoScript 10 is still a WIP in somewhat early stages. You might want to read the recent threads here to get a sense of what the current issues are.

Good question.
A bit of a catch-22, perhaps?

10 will only run in 57+.
5 will not run in 57.

So if you have 5 installed, when 57 installs NoScript would be disabled as 5 is "Legacy".

Presumably NoScript would (at some point) automatically update (with default update settings), which would then install 10, at which you'd expect it to be back "working".


Funny.
You presumably want NoScript for its "protections", yet on first run of 57 (or who knows when thereafter), you're not protected.

So for an existing user, looking for, expecting a "straight" update from 56 to 57, including a working NoScript - from the get-go, seems that is not going to happen.

I got the answer.

In both of my computers (W10 and W7), I waited updating to Firefox 57 until after NoScript 10 was released. As Firefox updated to 57, NoScript 5 updated automatically to version 10. The process worked out prety smoothly. Settings were imported automatically but in my W10, settings got corrupted. In W7, all went well.

So, Guest, if you are using version 5 in Firefox 56, update to 57, thats all you ll need to do.

Bo

So, Guest, if you are using version 5 in Firefox 56, update to 57, thats all you ll need to do.

And looking further, I believe that is the case also.

5 in 56 will not update to 10.
An [extension] "check for updates" in 56 will not find the update to 10.

What it looks like happens is...

on the 1st run of 57
(& I'm thinking before it even loads your Profile)
it goes out & checks for updates
knowing that it is 57, it says, hey, there's an update to 10
it downloads that into /staged/
then installs from there
then your Profile actually loads
with 10 preloaded


So in that respect, it seems (so long as an update exists) you are not left unprotected.


(I tested this in an otherwise, new, empty Profile, with only NoScript 5 installed.
I could test it in a HUGE profile, that takes many minutes to load, but not.
I'm just going to assume what I've stated is basically correct, so it seems you would be protected from the "get-go".


Now differences between 5 & 10, 56 & 57, that's an entirely different matter.)

therube wrote: So in that respect, it seems (so long as an update exists) you are not left unprotected.

That was my experience. Another detail you might like to know, NoScript updated automatically even though I set addons not to update automatically.

Another thing. After updating to Firefox 57, there was no NoScript 5 legacy leftover to Remove/Uninstall.

Bo