Closed
Bug 693897
Opened 13 years ago
Closed 13 years ago
Allow addons to opt-in to strict compatibility checking
Categories
(Toolkit :: Add-ons Manager, defect)
Toolkit
Add-ons Manager
Tracking
()
VERIFIED
FIXED
mozilla10
People
(Reporter: Unfocused, Assigned: Unfocused)
References
Details
(Keywords: addon-compat, dev-doc-complete, Whiteboard: [qa!])
Attachments
(3 files)
With addons defaulting to compatible, addons need a way to opt-in to having the Addons Manager enforce strict compatibility checks - so the addon is only marked as compatible if it explicitly matches the addon's targetApplications compatibility data. This would be via a new field in install.rdf, named "strictCompatibility" (or something similar).
Assignee | ||
Comment 1•13 years ago
|
||
Attachment #570628 -
Flags: review?(dtownsend)
Updated•13 years ago
|
Attachment #570628 -
Flags: review?(dtownsend) → review+
Assignee | ||
Comment 2•13 years ago
|
||
https://hg.mozilla.org/integration/fx-team/rev/1fb831781a15
Flags: in-testsuite+
Flags: in-litmus-
Whiteboard: [fixed-in-fx-team]
Target Milestone: --- → mozilla10
Assignee | ||
Comment 3•13 years ago
|
||
Here's a test addon that demonstrates the strictCompatibility option in install.rdf. It's compatible version range is Firefox 7.0 to 8.0. So it should *always* be marked as incompatible.
Assignee | ||
Comment 4•13 years ago
|
||
Another test addon - this has the strictCompatibility option, but it's set to false. So it should behave like any other addon that didn't have that option in isn't install.rdf.
Comment 5•13 years ago
|
||
https://hg.mozilla.org/mozilla-central/rev/41c52a9e1337
Status: ASSIGNED → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Whiteboard: [fixed-in-fx-team]
Updated•13 years ago
|
Keywords: dev-doc-needed
Comment 6•13 years ago
|
||
I updated: https://developer.mozilla.org/en/Install_Manifests#strictCompatibility https://developer.mozilla.org/en/Building_an_Extension#section_4 and https://developer.mozilla.org/en/Firefox_10_for_developers
Comment 7•13 years ago
|
||
Mozilla/5.0 (X11; Linux x86_64; rv:11.0a1) Gecko/20111121 Firefox/11.0a1 Mozilla/5.0 (X11; Linux x86_64; rv:10.0a2) Gecko/20111121 Firefox/10.0a2 Verified on Ubuntu 11.10, Mac OS 10.7, Windows XP and Windows 7 using the examples add-ons provided in the attachment and adding the string to existing add-ons in install.rdf. 1. Start Firefox 7 or 8 with a clean profile. (if upgrading to F10 set the extensions.strictCompatible pref to true) 2. Install an add-on with strictCompatibility set to true and an add-on with the pref set to false in install.rdf 3. Manually upgrade to Firefox 10/11. When <em:strictCompatibility> is set to true, the add-on is listed as incompatible even with extensions.strictCompatibility enabled. When <em:strictCompatibility> is set to false, the add-on is listed as compatible with extensions.strictCompatibility enabled.
Status: RESOLVED → VERIFIED
Whiteboard: [qa!]
You need to log in
before you can comment on or make changes to this bug.
Description
•