Closed
Bug 629873
Opened 15 years ago
Closed 15 years ago
Disabled Add-ons not sorted alphabetically
Categories
(Toolkit :: Add-ons Manager, defect)
Toolkit
Add-ons Manager
Tracking
()
VERIFIED
FIXED
mozilla2.0b12
People
(Reporter: luke.iliffe, Assigned: mconley)
References
Details
Attachments
(1 file)
357.26 KB,
image/png
|
Details |
If I have some disabled add-ons they are not always sorted alphabetically. This only seems to occur if one of the disabled add-ons is marked incompatible with minefield. In this case it is always listed above the compatible disabled add-on.
I thought the purpose of bug 624808 was to make a long list of add-ons broken into 2 lists based on their enabled state, each of those lists being sorted alphabetically. If each of the state lists has other criteria (such as compatibility) being taken into account during sorting this makes it more complicated and could make an individual add-on harder to find.
STR:
1. Open New Profile, go to about:addons
2. Search for and install the add-on compatibility reporter, don't restart
2. Search for and install aero window title, restart browser.
3. Install an incompatible add-on, e.g. Undo Closed Tabs Button https://addons.mozilla.org/en-US/firefox/addon/3082/
4. Restart browser
5. Disable aero window title and Undo closed tabs button, restart browser
Expected:
Alphabetically sorted disabled addons (AWT first UCTB underneath)
Actual:
Undo closed tabs button add-on is listed first.
Reporter | ||
Comment 1•15 years ago
|
||
Aggh! I have just reread bug 624808 comment 0 and it says:
"Instead, add-ons should be grouped with add-ons of similar status, as follows:
1. Top of list view: enabled add-ons
2. Second in list view: incompatible add-ons
3. Third in list view: disabled add-ons
4. Bottom of list view: blocked add-ons"
So this may actually be by design, but it still feels slightly wonky when looking at the list. Would if be clearer without the incompatible grouping, is this a likely category users are going to want to search for?
Comment 2•15 years ago
|
||
This ended up getting fixed by bug 629521
Comment 4•15 years ago
|
||
Verified fixed with Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:2.0b12pre) Gecko/20110210 Firefox/4.0b12pre
Status: RESOLVED → VERIFIED
OS: Windows 7 → All
Hardware: x86 → All
You need to log in
before you can comment on or make changes to this bug.
Description
•