Closed
Bug 603515
Opened 14 years ago
Closed 7 years ago
With automatic updates disabled for add-ons, offer available updates when browser compatibility changes
Categories
(Toolkit :: Add-ons Manager, defect)
Toolkit
Add-ons Manager
Tracking
()
RESOLVED
INACTIVE
Tracking | Status | |
---|---|---|
blocking2.0 | --- | - |
People
(Reporter: whimboo, Unassigned)
References
Details
Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:2.0b7pre) Gecko/20101006 Firefox/4.0b7pre
If the user has set add-ons to get updated manually we should only update those add-ons when the browser compatibility version changes. Similar to the automatic update path the list of available updates should be shown in the migration dialog during start-up. Right now we do not show any of the available updates.
Reporter | ||
Updated•14 years ago
|
blocking2.0: --- → ?
Comment 1•14 years ago
|
||
The compatibility UI offers to find available updates for the extensions that are incompatible doesn't it? You just have to click yes or something.
Don't see anything new here so we wouldn't block on it.
blocking2.0: ? → -
Reporter | ||
Comment 2•14 years ago
|
||
When I install Mozmill 1.4.1 in 4.0b7pre I don't get Mozmill 1.5.0 offered when upgrading to a 4.0b8pre build.
Steps:
1. Fresh profile with checkCompatibility turned off
2. Install Mozmill 1.4.1 (https://addons.mozilla.org/en-US/firefox/addon/9018/versions/?page=1#version-1.4.1)
3. Restart Firefox and turn on checkCompatibity + additional restart to disable the extension
4. Start a 4.0b8pre build
The migration wizard comes up but no compatibility updates are offered. Actually it doesn't matter if the add-on is set to update automatically or manually.
Comment 3•7 years ago
|
||
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.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → INACTIVE
You need to log in
before you can comment on or make changes to this bug.
Description
•