Eice wrote:I notice that the version numbers reported on the NoScript homepage and on AMO are different, with the one on the homepage being the newer. Is it a normal occurrence for versions uploaded to AMO to lag behind the latest versions?
Yes. Not always, but it happens. There can be a lag in getting stuff through AMO, a process I've never dug into, although Giorgio could give you the details if you really needed them. Just to make sure, though, we *are* talking about "Latest stable release" (which is marked as such), and not
"Latest development build", which is for those willing to test it before it is officially released to AMO, correct? Sometimes those two will be the same: the dev build *is* the stable release. Just wanted to make sure you weren't comparing a test build version # to the AMO version #, which is always the approved stable build.
Eice wrote:Also, if I download the copy provided on the NoScript homepage, will I still receive update notifications for NoScript via Firefox's update system?
Thanks in advance.
If you have a version number equal to or greater than the one at AMO, the updater reads that and has no need to notify you. If subsequently, a version is released through AMO that is more current than yours, the fact that you might previously have d/l from NS page won't prevent you from being notified, if that was a concern. Always want you to have the latest stable build (and welcome those willing to test dev. builds and report any bugs).
You're very welcome.
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US at an expert level; rv:1.8.1.20) Gecko/20081217 Firefox/2.0.0.20 diehard