You have received this email because you are a registered add-on developer on and you have at least one legacy extension associated with your account. You can find more information about porting legacy extensions to the WebExtensions API on MDN, and we encourage you to visit our wiki for more information about upcoming development work and how to get in touch with our team if you need any help. Once your new version is submitted to AMO, users who have previously installed your extension will automatically receive the update and your listing will appear in the gallery. Once this happens, users will no longer be able to find your legacy versions on AMO.Īfter legacy add-ons are disabled, you will still be able to port your extension to the WebExtensions APIs. All legacy add-on versions will be disabled by early October 2018.
On September 6, 2018, submissions for new legacy add-on versions will be disabled. Mozilla will stop supporting Firefox Extended Support Release (ESR) 52, the final release that is compatible with legacy add-ons, on September 5, 2018.Īs no supported versions of Firefox will be compatible with legacy add-ons after this date, we will start the process of disabling legacy add-on versions on AMO. You are receiving this email because you are listed as a developer of a legacy add-on on (AMO). News from the friendly crackpots over at Mozilla: By Bzzz In editorial note addon api compatibility firefox mozilla theme changer thunderbird webextensions xul Mozilla Firefox/Thunderbird “legacy” addons (#E6F3)
0 kommentar(er)
