Closed Bug 595847 Opened 14 years ago Closed 7 years ago

Cannot choose order of items in Add-ons Manager

Categories

(Toolkit :: Add-ons Manager, defect)

defect
Not set
normal

Tracking

()

RESOLVED WONTFIX

People

(Reporter: bugzilla, Assigned: qheaden)

References

Details

User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-US; rv:1.9.2.8) Gecko/20100722 Firefox/3.6.8 Build Identifier: Mozilla/5.0 (X11; Linux i686 on x86_64; rv:2.0b5) Gecko/20100101 Firefox/4.0b5 Greasemonkey is trying its hardest to integrate properly with the new Add-ons Manager API in Firefox 4. To date, we've followed the SlipperyMonkey (http://www.oxymoronical.com/blog/2010/07/How-to-extend-the-new-Add-ons-Manager) example. Today, in 4.0b5, it appears to be impossible to choose the order of the items in the manager. This is occasionally very important for user scripts -- one may change the page in a way that breaks the other, but not vice versa. There appears to be no way in the published interface to control which order the items display in: they are always forced into an alphabetical-by-name order. This breaks Greasemonkey. Reproducible: Always
Needed for search engine integration too
Blocks: 552747
Status: UNCONFIRMED → NEW
Component: General → Add-ons Manager
Ever confirmed: true
OS: Linux → All
Product: Firefox → Toolkit
QA Contact: general → add-ons.manager
Hardware: x86_64 → All
Version: unspecified → Trunk
Quentin is working on this as part of bug 335781.
Assignee: nobody → qheaden
Status: NEW → ASSIGNED
Since reporting this, we've worked around this by re-implementing the sort bar, which was removed in one of the betas before 4.0 was final, and adding somewhat clunky context menu items.
This isn't possible with WebExtensions and we are working towards a new add-ons manager that doesn't use XUL. That and given the 6 years since the last comment on this bug, makes me think this isn't going to happen.
Status: ASSIGNED → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.