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.
0 kommentar(er)
