Legacy extension that do continue to update, have to come from somewhere else. Updating & blocking are two different things.Īs Mozilla deleted all non-webextension extensions (aka "Legacy") you will never find updates for legacy extensions (to a Mozilla server) from a (Mozilla) update check.
I'm not sure whether official builds of newer Pale Moon talk to Mozilla's servers, as I do not run an OS which supports newer PM, but based on the message from SeaMonkey, I would say that SM still does.
The proof of this is that some other extensions which I have in that browser are saying "No Updates Available" when I ask to check, though I know that updates for at least a couple are in fact available and are compatible with Basilisk.įurthermore, an Extension from a PM dev DID offer and successfully delivered an update, i.e.
MY theory is that Basilisk in general (not just Tam's rebuild) does not talk to Mozilla's servers. The reason as explained seems logical, and in this case, Mozilla may have done a good thing, reacting quickly to a reported concern.įWIW, the alleged behaviour of the extension had not yet inflicted itself upon me and my portable edition of FF 52.9.0 ESR. I have other extensions which can do the same job as FVD (sometimes better, depending upon which browser and which versions of the browser and those other extensions), but thought that I would report what had occurred, since FVD is a popular addon, and as this had happened due to a different issue than a bug in FireFox 66. I dismissed the message, but not before following and reading a series of linked pages, which I will present next below : It said that the extension had been disabled due to security, stability, or performance reasons (did not specify which at that point), and suggested that I exit and restart FF. Suddenly, the other day, amid all of the kerfuffle about a newer FireFox version disabling extensions en masse, I get a message after launching the browser, and without trying to use the extension in that session. This version of FF and the FVD extension Version 16.3.7 had been getting along fine since January 26 of this year, when I had last updated and confirmed the operation of FVD, an extension which I and many others have used and trusted for years upon years.
0 kommentar(er)
