Confirm
587
edits
Changes
no edit summary
|Feature version=Firefox 10
|Feature health=OK
|Feature status note=Changes landed (and enabled) on both Aurora (10) and Nightly (11). This feature is currently preffed off in Aurora until testing shows the feature stable on Nightly.
}}
{{FeatureTeam
See [https://wiki.mozilla.org/Features/Add-ons/Add-ons_Default_to_Compatible/Detection_and_Mitigation Detection and Mitigation] for the current plan.
|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.
The ACR should be revamped to better fits its new role of reporting when add-ons are not compatible, rather than when they are compatible. For example, when a user disables an add-on, it should provide a user with the opportunity to say it's because it doesn't work. And it should look for other signs of incompatibility, similar to the self-tests.
|Feature implementation notes=* Add-ons Manager bug: {{bug|692664}} ([https://bugzilla.mozilla.org/showdependencytree.cgi?id=692664 Dependency tree])
* In order to land in 10 requiresRemaining bugs that need fixed before release** <s>{{bug|698653706387}}</s> Flip extensions.strictCompatibility pref in Firefox to make addons compatible-by-default (one-line patch to turn Send the feature on)** <s>{{bug|695977}}</s> Addons shouldn't be compatible by default compatibility mode when their minVersion is greater than the app version (I think the patch is done, but I've been holding off because half the logic is in the patch for {{bug|527141}}, which is unfinished and I need to make sure I haven't missed anything)** <s>{{bug|700201}}</s> Addons that haven't been updated for an extremely long time should not be compatible by default (<s>only recently filed, haven't started work on it yet, but it's </s>pretty simple)using AMO Search API* Preferable to also have** {{bug|693906}} Parse and use new compatibility ranges in AMO metadata ping (Still working on this, patch needs a bunch more Future work and some additional tests. AMO side is done, with some followup bugs found by QA)** {{bug|527141}} Addon update check should take into account compatibility preferences. Patch ready. Depends on AMO <s>{{bug|698355}}</s>* Nice to have:
** {{bug|570033}} Consider exposing add-on compatibility checking status of the browser.
** {{bug|695581}} Self-test to ensure compatible-by-default addons are working correctly
* AMO bug: {{bug|691834}} ([https://bugzilla.mozilla.org/showdependencytree.cgi?id=691834 Dependency tree])
** <s>{{bug|698355}}</s> in order to update addons that are compatible-by-default
** <s>{{bug|698358}}</s> in order to update the small sub-section of addons that opt-in to strict compatibility (none now, hopefully very few in the future, but something we need to fully support)
** {{bug|706385}} to make AMO search within the Add-ons Manager return all compatible results
}}
{{FeatureInfo
|Feature products status=Ready for resourcing & implementation
|Feature products notes=From the desktop side, we would like this to be prioritized as a P1 and part of achieving "silent update".
|Feature engineering status=ImplementingFinishing up last loose ends|Feature engineering notes=Implementing stuff that doesn't depend on data from AMOMost of this is done, just finishing up some final loose ends.
|Feature security status=sec-review-unnecessary
|Feature security health=OK
