670302 - Provide some indication whether there are incompatible add-ons on the first page before clicking the update button

Status: RESOLVED WONTFIX

(Toolkit :: Application Update, defect)

Description

[WBT]

The "Software Update" window that informs users an update is available with options to "Ask Later" or "Update Firefox" should also show users which of their extensions are incompatible with the new version, and note that all other extensions (or all extensions, if appropriate) are compatible.

This respects users' agency to make an informed decision about updating, and helps users who are wary of add-on incompatibility.

It needs to come in the initial dialogue window where the user still has a full choice between "Ask Later" or "Update Firefox."  There is NO indication that clicking "Update Firefox" will perform a compatibility check, and there is a sense that it could be an irreversible click that breaks add-on functionality. 

See user story and discussion at related bug 670231.

Comment 1

[Robert Strong (they/them - no direct email)]

The Add-on compatibility check occurs very quickly and is already shown. Sounds more like you want the update ui to provide some indication whether there are incompatible add-ons on the first page before clicking the update button so changing summary.

Comment 3

[WBT]

The add-on compatibility check is not done and automatic updates are breaking add-ons seen to have core functionality.
I am not the only one observing this.  For example, see: 
https://forums.zotero.org/discussion/27989/
https://addons.mozilla.org/en-us/firefox/addon/tabgroups-manager/reviews/

There are pages of reviews just from people who were updated to FF20 and found their core functionality missing.  Upgrade development was accelerated, but for the latter link the original developer is gone and Mozilla moderators pulled the link that another user had posted to the updated extension.

WORKAROUND:
Downgrade and disable all future updates, until you can find out pre-update which add-ons will stop working.

Comment 4

[Robert Strong (they/them - no direct email)]

Likely due to bug 692664 and outside the control of app update.

fligtar / unfocused: can one of you check if the add-ons listed in comment #3 would be compatible by default?

Comment 5

[WBT]

Actually, it's possible that Bug 692664 may be the cause of the problems on this particular occasion; thanks for making that link.  It used to be that you got at least some notice that the add-on would not be functional with the new version, though after you'd already passed the "point of no return" on the update.  Now you just update and don't get any notice, but the functionality is broken.

Comment 6

[Robert Strong (they/them - no direct email)]

The app update add-on compatibility check will be removed in bug 1262880