My anti-virus program updates much more frequently than that. If you want to dely the WebExtensions switch it’s way better to switch to 52 ESR than stay on v56 with security issues.įirefox updates about every six weeks. Using not up-to-date Firefox is dangerous, you can catch malware or be hacked. xpis.īut get it soon because it won’t be around in Fx v57. To save all your current extensions in Fx v56, you may want to try my FEBE extension to backup those add-ons as install-able. So now it looks like, not only have I had to download FF56, but I’m going to have to download all the XPIs too in case I need to install elsewhere.Īnother case of scorching the earth and salting it as you move forward preventing anyone who disagrees with you from being able to go their own way without someone investing a huge amount of effort. There won’t be a Mozilla repository for legacy add-ons after we drop support, but the add-ons are currently available if anyone outside of Mozilla wants to try to create one. Will there be any repository we can go to to install non-WE extensions?įor AMO, we generally draw the line for support on ESR, and supporting legacy add-ons means maintaining a whole host of features that make the site very complex and hard to work with. So users can’t see themĭoes this mean ‘legacy’ add-ons will eventually disappear from AMO? What about users (like myself) that have turned off automatic updates and will only use Fx v56 for the foreseeable future. Remove legacy extensions from the extensions site. I would like my extensions back, please 🙁 Tags: amo, compatibility, developers, esr, firefox 57, webextensionsĬategories: compatibility, developers, webextensions 42 responses There are big changes coming to AMO, including a completely new design. This means some legacy features may also change during this time period. However, AMO will primarily focus on WebExtension add-on listings. There will be no override provided for this behavior.ĪMO ( ) will continue to support legacy add-on listings throughout the ESR 52 cycle. The following ESR release (60), and any subsequent release, will not support legacy add-ons.Support for ESR 52 officially ends on August 2018. ESR 52 will be the last ESR release that supports legacy add-ons.To clarify how legacy extensions will work with the ESR release: However, we have received some questions from developers on how this timeline applies to the Firefox Extended Support Release (ESR). As anticipated, Firefox 57 will be released in late November, only allowing add-ons using the WebExtensions API. Update: the next ESR was moved to coincide with Firefox 60 instead of 59.Įarlier this year, we shared with you our compatibility plan for Firefox.

If i disable add ons what will happen