Closed
Bug 546465
Opened 15 years ago
Closed 15 years ago
extensions.checkCompatibility.<version> to disallow very old extensions
Categories
(Toolkit :: Add-ons Manager, defect)
Toolkit
Add-ons Manager
Tracking
()
RESOLVED
WONTFIX
People
(Reporter: VinnieCool, Unassigned)
References
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2) Gecko/20100115 Firefox/3.6 (.NET CLR 3.5.30729)
Build Identifier: Trunk
It was the right step to change extensions.checkCompatibility to extensions.checkCompatibility.<version> even though it added a little more complexity. The configuration may be extended to include the minimum version number required for an extension to work with a particular firefox version. E.g. by setting extensions.checkCompatibility.3.6pre=3.5 (instead of false) should allow extensions with maxVersion from 3.5 to 3.6pre but not with maxVersion less than 3.5. The rationale behind this is that the tester might be testing her 3.5 compatible extension to see if that still works with 3.6pre but may not want to crash Firefox with an older extension from 3rd party or her own. The same can be achieved by being vigilant, but why not use the automated solution when the version check code already exists.
Later when user upgrades to say 3.6, they have to add a new setting for the new version (just like it works now) otherwise Firefox will assume extensions.checkCompatibility.3.6=3.6 (this may be not actually exist in the js fie)
Reproducible: Sometimes
Comment 1•15 years ago
|
||
I don't think the functionality proposed warrants the additional complexity that this would introduce. The versioned pref is already a little confusing to people and changing it this way would make it more so, additionally the implementation would not be trivial I think and this is at the end of the day meant to be a simple means for developers and testers to get around some limitations, we don't want to spend the time maintaining this much and more complex code would mean we have to invest more time in this.
Status: UNCONFIRMED → RESOLVED
Closed: 15 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•