Closed
Bug 961999
Opened 11 years ago
Closed 7 years ago
Make extensions.checkCompatibility only apply to specific add-ons
Categories
(Toolkit :: Add-ons Manager, defect)
Toolkit
Add-ons Manager
Tracking
()
RESOLVED
INACTIVE
People
(Reporter: Unfocused, Unassigned)
References
Details
Right now, extensions.checkCompatibility is a rather large and indiscriminate hammer - affecting *all* add-ons. Now that we have compatible-by-default, and we know it's working remarkably well (woo!), we can reconsider how the checkCompatibility pref works. I think it still has it's uses, but should be used as a last resort - so instead should be made to be a lot more specific, affecting only specific add-ons. ie:
extensions.checkCompatibility.<APPVERSION>.<ADDONID> = false
There's the question of whether we should have a variant that limits it to a given add-on version too:
extensions.checkCompatibility.<APPVERSION>.<ADDONID>.<ADDONVERSION> = false
But I'm sceptical of how often this would be used given the pref that doesn't include the add-on version, which is easier to use. And requiring the add-on version may be *too* annoying at this stage. So it's probably not worth implementing at the moment.
(See bug 956990 comment 2 for more background thoughts on this general problem.)
Comment 1•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
•