On installing a new version, we display a dialog box asking the user to wait while we check compatibility of their add-ons with the new application version. We should list the add-ons that are not known to be compatible (that is, those that need to be disabled in the new application version unless we can find an upgrade or updated compatibility information).

So what would be the workflow here, because we should check for updates to add-ons before a user even updates. Right now lets say a user is using Firefox 22 and Addon X v1, which isn't compatible with Firefox 24. Add-on X v1.1 exists for Firefox 24 though. The User checks for updates, and is warned the add-on will be disabled, but no message is given that the Add-on will update after Firefox updates. We should make Firefox check for add-on updates before warning about incompatibilities, and download and install those updates silently. Apologies if this is what you meant ;)

(In reply to Tyler Downer [:Tyler] from comment #1) > We should make Firefox check for add-on updates before warning about > incompatibilities, and download and install those updates silently. Something like that is a desired end state; see bug 760346 and bug 890100. The discussion in bug 760346 covers most of the known problems, but the end result is that sometimes we have no choice but to either disable or upgrade add-ons at startup time. On the other hand, bug 772484 (and some others) is about problems we have with upgrading add-ons at startup time; we'd like to give the user a chance to skip the update if they want, with the understanding that some add-ons will need to be updated later. This bug follows on from that work.

Per policy at https://wiki.mozilla.org/Bug_Triage/Projects/Bug_Handling/Bug_Husbandry#Inactive_Bugs. If this bug is not an enhancement request or a bug not present in a supported release of Firefox, then it may be reopened.