Canmove, confirm, emeritus
1,043
edits
Changes
no edit summary
{{FeatureStatus
|Feature name=Add-ons Default to Compatible
|Feature stage=DraftDefinition|Feature status=In progress|Feature version=Firefox 910
|Feature health=OK
|Feature status note=Soliciting Final feedbackround.
}}
{{FeatureTeam
}}
{{FeaturePageBody
|Feature open issues and risks=What mitigations are needed to detect and fix truly incompatible add-on negative effects? Some number of extensions out there in the dark matter will be genuinely incompatible and some number of those incompatible extensions will be broken in ways that may not be easy for the user to manage through or around.
|Feature overview=The vast majority of add-ons work from one version of Firefox to the next without the need for developer maintenance, but under the current system, compatibility information must be updated in order for Firefox to enable the add-on for use. For add-ons hosted on AMO, this is done automatically. However, 75% of add-ons in use are not hosted on AMO, and are therefore a major compatibility obstacle for our users. All of the compatibility effort put into each release is simply because Firefox still assumes add-ons will be incompatible between versions, when they usually aren't.
When users upgrade to a new version of Firefox, only the add-ons that are actually incompatible should be disabled, and the rest are assumed to be compatible. Because Nightly, Aurora, and Beta users will test out the add-ons for weeks before stable users, we should be able to identify and blacklist incompatible add-ons before stable users would be affected by a truly incompatible add-on.
|Feature non-goals=This plan is not trying to solve the issue of binary compatibility between releases.
|Feature functional spec=''Firefox''
When Firefox wants to update to a new version, it should determine which add-ons are incompatible and which will be assumed compatible by looking at the following:
}}
{{FeatureTeamStatus
|Feature products status=Collecting feedback.
|Feature products notes=From the desktop side, we would like this to be prioritized as a P1 and part of achieving "silent update".
}}
