Currently, the URL for the discover pane is hardcoded. It should come from prefs (so it can be overwritten) and have the usual variables replaced.
Oops, this was fixed awhile ago. http://hg.mozilla.org/projects/addonsmgr/rev/aac130bb8238
Whiteboard: [rewrite] → [rewrite][fixed-in-addonsmgr]
Blair, what happened with all the extensions.getAddons.* prefs? Don't we need those anymore? Means there is no link in the UI which redirects us to AMO?
(In reply to comment #2) > Blair, what happened with all the extensions.getAddons.* prefs? Don't we need > those anymore? Means there is no link in the UI which redirects us to AMO? Most of these are irrelevant now. Although, I'll be adding a couple back for bug 561237.
Landed on trunk as a part of bug 554007
Status: NEW → RESOLVED
Last Resolved: 9 years ago
Resolution: --- → FIXED
Whiteboard: [rewrite][fixed-in-addonsmgr] → [rewrite]
Target Milestone: --- → mozilla1.9.3a5
Verified fixed by checkin. Litmus tests for the discovery pane will be covered by other bugs.
Status: RESOLVED → VERIFIED
Browser_discovery.js checks that the url is loaded correctly and has the add-on data in it.
Flags: in-testsuite? → in-testsuite+
You need to log in before you can comment on or make changes to this bug.