Confirmed users
587
edits
Features/Add-ons/Add-ons Default to Compatible: Difference between revisions
Jump to navigation
Jump to search
m
Features/Add-ons/Add-ons Default to Compatible (view source)
Revision as of 00:27, 7 October 2011
, 7 October 2011no edit summary
No edit summary |
mNo edit summary |
||
| Line 47: | Line 47: | ||
'''Add-on Compatibility Reporter'''<br/> | '''Add-on Compatibility Reporter'''<br/> | ||
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}} | |Feature implementation notes=* Add-ons Manager bug: {{bug|692664}} | ||
AMO bug: {{bug|691834}} | * AMO bug: {{bug|691834}} | ||
}} | }} | ||
{{FeatureInfo | {{FeatureInfo | ||