Closed Bug 632650 Opened 14 years ago Closed 14 years ago

Add-ons Manager 'by state' grouping should be simpler or include some explanation

Categories

(Toolkit :: Add-ons Manager, defect)

x86
Windows 7
defect
Not set
normal

Tracking

()

VERIFIED DUPLICATE of bug 629873

People

(Reporter: tawn, Unassigned)

Details

User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:2.0b11) Gecko/20100101 Firefox/4.0b11 Build Identifier: Mozilla/5.0 (Windows NT 6.1; rv:2.0b11) Gecko/20100101 Firefox/4.0b11 In Firefox 4.0b11, with the new grouping implemented by Bug 624808, my add-ons get listed in the following order: Enabled add-ons (includes incompatible, force-enabled) Add-ons that are both incompatible and disabled Add-ons that are disabled (but not incompatible) Somewhat complex ordering considering there is no explanation of the sort-order. Reproducible: Always Steps to Reproduce: 1. Have lots of add-ons installed in various states 2. Open add-ons manager Actual Results: 1. Wonder why my add-ons got all jumbled like that 2. Take time to figure out the sort order Expected Results: A less complex sort, an option for a basic alphabetical sort, sub-headings, or some other explanation of what the sort-order is. (Less initial confusion)
This got fixed in bug 629873 and bug 629521 I believe
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → DUPLICATE
custom.firefox.lady, does the latest changes Dave pointed out makes it clearer for you? Not sure if we can easily insert sub-headings for the different buckets.
(In reply to comment #2) > does the latest changes Dave pointed out makes it clearer > for you? Indeed it does. > Not sure if we can easily insert sub-headings for the different > buckets. Its a richlistbox, not a table, so I suspected that already. Just tried to give some examples.
In the future we will probably have a drop down again which can be used to select different sortings. So that would probably be enough. For Firefox 4 this will now be fixed. Thanks!
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.