None of the columns sort correctly in Download Manager. Results are pretty random.



Download & File Handling
14 years ago
12 years ago


(Reporter: Bud Simrin, Unassigned)


Mac OS X

Firefox Tracking Flags

(Not tracked)




14 years ago
User-Agent:       Mozilla/5.0 (000000000; 0; 000 000 00 0 000000; 00000; 0000000) Gecko/20031208
Build Identifier: Mozilla/5.0 (000000000; 0; 000 000 00 0 000000; 00000; 0000000) Gecko/20031208

If I click on, say, Name, the results are not alphabetical, but random. If I
click on Progress, ditto. Etc. Also, the current download does not usually
appear at the top or the bottom even if sorted by Progress. There are also a few
blank lines that usually get sorted to the top or bottom but which start in
random places.

Reproducible: Always

Steps to Reproduce:
1. From Tools Menu, click on Download Manager
2. Try to sort on any column

Actual Results:  
Randomly sorted downloads list

Expected Results:  

Nothing special I can think of. This problem has persisted since early versions
of Mozilla.

Comment 1

13 years ago
WFM in Mozilla 1.8a4 (8/28/04 build) under MacOSX 10.3.5.

-- David Lawhon

Comment 2

13 years ago
I'm using Mozilla ver 1.7.2 now under OS 10.2.8 and the Download Manager sorts are better but still 
have problems. NAME sorts perfectly now (at least, today). However, PROGRESS still sorts randomly 
(Finished, Failed, Complete) and TRANSFERED sorts alphabetically rather than numerically.
Product: Browser → Seamonkey

Comment 3

13 years ago
Also occurs on PC platform (Mozilla 1.7.3 & previous)

Bugs 207448, 207683, 215716, 212896 appear to be different statements of the
same problem
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Last Resolved: 12 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.