Confirmed users
587
edits
Features/Add-ons/Add-ons Default to Compatible: Difference between revisions
Jump to navigation
Jump to search
Features/Add-ons/Add-ons Default to Compatible (view source)
Revision as of 01:53, 12 December 2011
, 12 December 2011no edit summary
(Added links to Detection and Mitigation proposal.) |
No edit summary |
||
| Line 5: | Line 5: | ||
|Feature version=Firefox 10 | |Feature version=Firefox 10 | ||
|Feature health=OK | |Feature health=OK | ||
|Feature status note=Changes landed on Aurora (10) and Nightly (11) | |Feature status note=Changes landed (and enabled) on both Aurora (10) and Nightly (11). | ||
}} | }} | ||
{{FeatureTeam | {{FeatureTeam | ||
| Line 19: | Line 19: | ||
See [https://wiki.mozilla.org/Features/Add-ons/Add-ons_Default_to_Compatible/Detection_and_Mitigation Detection and Mitigation] for the current plan. | 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. | |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. | ||
| Line 55: | Line 54: | ||
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. | 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]) | |Feature implementation notes=* Add-ons Manager bug: {{bug|692664}} ([https://bugzilla.mozilla.org/showdependencytree.cgi?id=692664 Dependency tree]) | ||
* | * Remaining bugs that need fixed before release | ||
** | ** {{bug|706387}} Send the compatibility mode when using AMO Search API | ||
* Future work: | |||
* | |||
** {{bug|570033}} Consider exposing add-on compatibility checking status of the browser. | ** {{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]) | * AMO bug: {{bug|691834}} ([https://bugzilla.mozilla.org/showdependencytree.cgi?id=691834 Dependency tree]) | ||
| Line 69: | Line 64: | ||
** <s>{{bug|698355}}</s> in order to update addons that are compatible-by-default | ** <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) | ** <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 | {{FeatureInfo | ||
| Line 82: | Line 78: | ||
|Feature products status=Ready for resourcing & implementation | |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 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= | |Feature engineering status=Finishing up last loose ends | ||
|Feature engineering notes= | |Feature engineering notes=Most of this is done, just finishing up some final loose ends. | ||
|Feature security status=sec-review-unnecessary | |Feature security status=sec-review-unnecessary | ||
|Feature security health=OK | |Feature security health=OK | ||