canmove, Confirmed users
1,635
edits
Features/Desktop/Add-on hotfix: Difference between revisions
Jump to navigation
Jump to search
Features/Desktop/Add-on hotfix (view source)
Revision as of 23:56, 28 October 2011
, 28 October 2011no edit summary
No edit summary |
No edit summary |
||
| Line 42: | Line 42: | ||
* Users should be unable to uninstall hofixes | * Users should be unable to uninstall hofixes | ||
* Hotfixes are shown with special UI in the add-ons manager | * Hotfixes are shown with special UI in the add-ons manager | ||
|Feature functional spec=* Firefox should look for "updates" for a particular add-on id | |Feature functional spec=* Firefox should look for "updates" for a particular add-on id | ||
* | * Firefox will check AMO for add-on updates if the add-on is already installed | ||
* The add-on id will be hardcoded | * The add-on id will be hardcoded | ||
* A pref will be set indicating the add-on has installed itself and the version. This gives a historical record and allows the add-on to uninstall itself if desired | |||
** We won't have the add-on uninstall itself for a particular version as Firefox would then redownload it again | |||
* Firefox will track the last installed add-on version in a special preference. This allows the add-on to uninstall itself while preventing Firefox from reinstalling it | * Firefox will track the last installed add-on version in a special preference. This allows the add-on to uninstall itself while preventing Firefox from reinstalling it | ||
* The add-on should never tell the user it is incompatible | |||
|Feature ux design=* None required | |Feature ux design=* None required | ||
* We should get sign-off on the fact that the add-on won't be treated specially and will show up in the add-on manager, can be disabled, etc | * We should get sign-off on the fact that the add-on won't be treated specially and will show up in the add-on manager, can be disabled, etc | ||
| Line 89: | Line 90: | ||
Based on all that so far I'm leaning towards using the update check call as it seems to suit our needs better right now." | Based on all that so far I'm leaning towards using the update check call as it seems to suit our needs better right now." | ||
|Feature landing criteria=* Need to test the add-on in a real-world scenario during aurora / beta | |Feature landing criteria=* Need to test the add-on in a real-world scenario during aurora / beta | ||
}} | }} | ||