Closed
Bug 302759
Opened 19 years ago
Closed 19 years ago
Remote maxVersion does not override install.rdf maxVersion during an upgrade
Categories
(Toolkit :: Add-ons Manager, defect)
Toolkit
Add-ons Manager
Tracking
()
RESOLVED
FIXED
mozilla1.8final
People
(Reporter: bugzilla, Assigned: robert.strong.bugs)
References
()
Details
(Keywords: regression, Whiteboard: [no l10n impact])
Attachments
(1 file)
4.82 KB,
patch
|
benjamin
:
review+
benjamin
:
approval1.8b4+
|
Details | Diff | Splinter Review |
When updating extensions, Deer Park does not check the remote maxVersion value (addons.mozilla.org) if the local maxVersion value (install.rdf) suggests incompatibility. Example (with Deer Park, 1.0+): MyExtension 0.1 with a maxVersion of 1.0 (install.rdf) MyExtension 0.2 with a maxVersion of 1.0 (install.rdf) and alternate maxVersion of 1.0+ (addons.mozilla.org) When Firefox checks for extension updates, it correctly identifies MyExtension 0.2 as being available from addons.mozilla.org and downloads it. Upon installation, a compatibility error is given instead of overriding the local maxVersion with the remote maxVersion. I believe this could be a regression, but cannot be sure. I'm pretty sure that it's the desired behaviour either way, please remove the keyword if appropriate. -> Robert Strong who has a fix for this.
Reporter | ||
Comment 1•19 years ago
|
||
Nominating to block 1.8b4 to avoid problems later.
Flags: blocking1.8b4?
Whiteboard: [no l10n impact]
Assignee | ||
Comment 2•19 years ago
|
||
_applyVersionUpdates checked for the existence of local target app info in the extensions datasource but never checked if the target app info is different when compared to the local item as in an upgrade.
Assignee | ||
Updated•19 years ago
|
Attachment #191049 -
Flags: review?(benjamin)
Assignee | ||
Updated•19 years ago
|
Summary: Remote maxVersion does not override install.rdf maxVersion → Remote maxVersion does not override install.rdf maxVersion during an upgrade
Updated•19 years ago
|
Attachment #191049 -
Flags: review?(benjamin) → review+
Assignee | ||
Updated•19 years ago
|
Whiteboard: [no l10n impact] → [checkin needed][a+][no l10n impact]
Updated•19 years ago
|
Flags: blocking1.8b4? → blocking1.8b4+
Assignee | ||
Updated•19 years ago
|
Attachment #191049 -
Flags: approval1.8b4?
Assignee | ||
Updated•19 years ago
|
Whiteboard: [checkin needed][a+][no l10n impact] → [no l10n impact]
Updated•19 years ago
|
Attachment #191049 -
Flags: approval1.8b4? → approval1.8b4+
Updated•19 years ago
|
Whiteboard: [no l10n impact] → [no l10n impact][checkin needed][a+]
Comment 3•19 years ago
|
||
Checking in nsExtensionManager.js.in; /cvsroot/mozilla/toolkit/mozapps/extensions/src/nsExtensionManager.js.in,v <-- nsExtensionManager.js.in new revision: 1.139; previous revision: 1.138 done
Whiteboard: [no l10n impact][checkin needed][a+] → [no l10n impact]
Target Milestone: --- → Firefox1.1
Assignee | ||
Comment 4•19 years ago
|
||
Fixed on trunk... thanks for the checkin Gavin
Status: NEW → RESOLVED
Closed: 19 years ago
Resolution: --- → FIXED
Updated•16 years ago
|
Product: Firefox → Toolkit
You need to log in
before you can comment on or make changes to this bug.
Description
•