Confirm
2,473
edits
Changes
no edit summary
|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 requires
** {{bug|698653}} Flip extensions.strictCompatibility pref in Firefox tomake addons compatible-by-default (one-line patch to turn the feature on)** {{bug|695977}} Addons shouldn't be compatible by default when theirminVersion 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 missedanything)** {{bug|700201}} Addons that haven't been updated for an extremely longtime should not be compatible by default (only recently filed, haven'tstarted work on it yet, but it's pretty simple)
* Preferable to also have
** {{bug|693906}} Parse and use new compatibility ranges in AMO metadataping (Still working on this, patch needs a bunch more work and someadditional tests. AMO side is done, with some followup bugs found by QA)** {{bug|527141}} Addon update check should take into account compatibilitypreferences. Patch ready. Depends on AMO {{bug|698355}}
* Nice to have
** {{bug|570033}} Consider exposing add-on compatibility checking status ofthe browser.
* AMO bug: {{bug|691834}} ([https://bugzilla.mozilla.org/showdependencytree.cgi?id=691834 Dependency tree])
* In order to land in 10 requires
** {{bug|698355}} in order to update addons that are compatible-by-default
** {{bug|698358}} in order to update the smallsub-section of addons that opt-in to strict compatibility (none now, hopepfully very few in the future, but something we need to fully support)
}}
{{FeatureInfo
