Closed
Bug 635108
Opened 13 years ago
Closed 5 years ago
We no longer support extensions.%ID%.update.enabled
Categories
(Toolkit :: Add-ons Manager, defect)
Toolkit
Add-ons Manager
Tracking
()
RESOLVED
WONTFIX
People
(Reporter: mossop, Unassigned)
References
Details
(Keywords: regression)
We used to in Firefox 3.6, we have lost it by accident in the rewrite. Do we want it back?
Comment 1•13 years ago
|
||
So similar to extensions.update.enabled it wouldn't match the UI we have in the add-ons manager?
Reporter | ||
Comment 2•13 years ago
|
||
(In reply to comment #1) > So similar to extensions.update.enabled it wouldn't match the UI we have in the > add-ons manager? There was never any UI for this setting.
Comment 3•13 years ago
|
||
(In reply to comment #2) > There was never any UI for this setting. So is this setting for completely disabling updates for that extension, even for the manual update case?
Comment 4•13 years ago
|
||
Yea, I'd imagine that would disable manual updates as well (and checking for updates). It seems pretty redundant - the UI now provides more control over updates, we no longer prompt for updates on startup, and developers can just not include an update URL if they want to not have it updated (er, and not list it on AMO). Only use I can think of beyond that is in an enterprise environment, to restrict users from upgrading a provided addon (eg, due to an outside dependency).
Updated•5 years ago
|
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•