A compatibility layer will *not* be built for add-ons to transition to the new EM API (bug 563412). This covers one type of add-on that will break in the new add-ons Manager. A lot of others will break for other reasons (see bug 562808). Conclusion: Make the Compatibility Reporter work with the new add-ons manager quickly!
The goal should be to keep a single XPI that is still compatible with builds before 3.7a5pre or whatever the Firefox version will be when it lands. This should be possible via separate overlays loaded via chrome.manifest flags.
Target Milestone: BW-1.1.2 → ACR-1.0
Version: BW-1.1.x → ACR-0.*
Dave, for now you can bypass bug 565610 by loading add-ons as chrome://mozapps/content/extensions/extensions.xul
Assignee: brian → dave
The compatibility reported should now be working with the new Add-ons Manager (but maintains compatibility with the legacy EM): - compatibility button showing on 3.7 in list view and detail view (themes and extensions). - submit dialog now using new AddonManager API in 3.7. - uninstall listener now using new AddonManager API in 3.7. - remains compatible with legacy Extension Manager stuff (< 3.7). Snags: - Only works in 3.7 when extensions manager loading like "chrome://mozapps/content/extensions/extensions.xul" (see https://bugzilla.mozilla.org/show_bug.cgi?id=565610) r67270.
Status: NEW → ASSIGNED
David, do we have a dev XPI somewhere we can use for testing?
(In reply to comment #4) > David, do we have a dev XPI somewhere we can use for testing? Yes, see: https://bugzilla.mozilla.org/attachment.cgi?id=448362 (attachment to bug 565610)
Created attachment 450640 [details] ACR compatible with 3.7a6pre New ACR XPI compatible with 3.7a6pre Reminder: only works correct when add-ons manager is loaded via this chrome url: chrome://mozapps/content/extensions/extensions.xul
The ACR makes other "incompatible" addons still working, but compatibility reporting does not work anymore.
Jan, please read the former comments. Everything points to bug 565610 which has to be fixed first. Meanwhile use the chrome url.
Status: ASSIGNED → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → FIXED
Tested with latest ACR development build and Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.3a6pre) Gecko/20100623 Minefield/3.7a6pre Now with bug 565610 fixed it looks good. The Compatibility button is visible and sending reports work. Marking as verified fixed.
Status: RESOLVED → VERIFIED
Also working on Win x64, tested with Mozilla/5.0 (Windows; U; Windows NT 6.0; Win64; x64; en-US; rv:2.0b2pre) Gecko/20100701 Minefield/4.0b2pre. Looks good :)
Product: addons.mozilla.org → addons.mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.