Update the flow for users with incompatible add-ons (now that we are default to compatible)

RESOLVED WONTFIX

Status

()

Toolkit
Application Update
RESOLVED WONTFIX
6 years ago
2 years ago

People

(Reporter: clee, Unassigned)

Tracking

12 Branch
mozilla13
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

6 years ago
Feature page: https://wiki.mozilla.org/Silent_Update_not_now_prompt

Although add-ons are default to compatible with Fx10, we will continue to check for add-ons that may be explicitly incompatible with new versions of Fx or add-ons that contain binary components.  

See the use case and requirements section on the feature page for details.
Component: Installer → Application Update
OS: Mac OS X → All
Product: Firefox → Toolkit
QA Contact: installer → application.update
Hardware: x86 → All
Target Milestone: Firefox 13 → mozilla13

Comment 1

6 years ago
will this be optional? because some addons will never will be updated
(eg bundled with antivirus or search bars)
because sometimes the addons work but the max data is set too low Min=10,Max=11
(should not be there IMHO only min is enough)
so if a user is set FF to auto update it should happen immediately(security patch?)
unless
the user has explicitly disabled updates(necessary for testing & stuff or having multiple versions for development)
Did this ever get implemented?
(In reply to Anthony Hughes, Mozilla QA (:ashughes) from comment #2)
> Did this ever get implemented?
Not yet, it is behind numerous other bugs that need to be fixed
Is there a blocker bug (or bugs) we can add to the dependency list?
No
Hrm...okay...
Hrm... we don't add dependencies for lack of resources to work on a bug or dependencies to a bug to bugs that are unrelated and are being worked on that have a higher priority.
(In reply to Robert Strong [:rstrong] (do not email) from comment #7)
> Hrm... we don't add dependencies for lack of resources to work on a bug or
> dependencies to a bug to bugs that are unrelated and are being worked on
> that have a higher priority.

I completely understand that but it wasn't clear to me by your previous responses that was the case. I understood from comment 3 that there were bugs physically blocking this work from being done, not that it was a development resource issue. Making this point clearer in the future might prevent such confusion.

Apologies for my misunderstanding.
Not a problem and sorry for not being clearer. For future reference, the app update component is very good about not leaving bugs opened that have been implemented so if you see it as still open then you can assume it hasn't been implemented. There is also a ton of other work going on so if a new feature is not actively implemented then you can assume it is because there is higher priority work taking precedence.
The app update add-on compatibility check will be removed in bug 1262880
Status: NEW → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.