> they will be limited to very popular add-ons and a limited number of other cases. > Yes, it should be activated soon on Nightly > No, the Add-ons Manager won’t show this. I tried to spot check some of what I think is high-profile add-ons (greasemonkey, stylish, noscript), but didn’t see any with such a label. Getting to amo from the add-ons manager doesn’t seem to be easy (I think you have to double click the add-on, click the ratings, and click the add-ons name in the right column). > There’s a green “Compatible with Firefox 57+” tag for all add-ons that use the new APIs. However, since the alternatives are hand-picked, they will be limited to very popular add-ons and a limited number of other cases. Yes, it should be activated soon on Nightly.
> – Are you going to add a “find alternative” feature to the add-ons manager, such that it will be easy to get suggestions for alternatives for add-ons that is not going to get updated? > Are you going to add this information to the Add-ons Manager? There’s a green “Compatible with Firefox 57+” tag for all add-ons that use the new APIs. If they have a listing page on AMO, you could look now, though it’s likely that versions that only work on 57 and above won’t be submitted at least for a few weeks. > – Is it possible that some of them have a version ready for 57 and above, and if so is there an easy way to see which? There will be a preference to turn them back on, but it will only work on Nightly. > – Will all Legacy add-ons be disabled in 57? – Are you going to add a “find alternative” feature to the add-ons manager, such that it will be easy to get suggestions for alternatives for add-ons that is not going to get updated? – Is it possible that some of them have a version ready for 57 and above, and if so is there an easy way to see which? Are you going to add this information to the Add-ons Manager? – Will all Legacy add-ons be disabled in 57? If i look in the Add-ons Manager there is 1 out of 12 enabled add-ons that is *not* marked Legacy (1 out out 21 if I include disabled add-ons). Tags: amo, compatibility, developers, documentation, firefox 57, webextensionsĬategories: compatibility, developers, documentation, webextensions 49 responses If you run into any compatibility issues, please file them here. We will be rolling out these changes in the coming weeks.Īdd-on compatibility is one of the most complex AMO features, so it’s possible that some things won’t work exactly right at first.
This is meant to reduce instances of users installing add-ons that will break within a few weeks. Add-ons built with WebExtensions APIs will eventually show up higher on search rankings.Also, we will give more prominence to the All Versions page, where older versions of the add-on are available. To address this, compatibility filters on search will be off by default. That can make it difficult for users of older versions of Firefox to find a compatible version. Some developers will be submitting ports to the WebExtensions API that depend on very recent API developments, so they may need to set a minimum version of 56.0 or 57.0. It will be easier to find older versions of add-ons when the latest one isn’t compatible.Related to this, you won’t be able to upload legacy add-ons that have a maximum version set higher than 56.*.They can still be installed on Nightly with some preference changes, but may break due to other changes happening in Firefox. This is the end of the line for legacy add-on compatibility.
All legacy add-ons will have strict compatibility set, with a maximum version of 56.*.In preparation for Firefox 57, a number of compatibility changes are being implemented on (AMO) to support this transition. There should be no expectation of legacy add-on support on this or later versions. And while it isn’t disabling legacy add-ons just yet, it will soon. Firefox 57 is now on the Nightly channel (along with a shiny new logo!).
0 kommentar(er)
