Closed
Bug 82702
Opened 23 years ago
Closed 23 years ago
download progress window does not cope with unknown lengths
Categories
(SeaMonkey :: UI Design, defect)
Tracking
(Not tracked)
People
(Reporter: robbe, Assigned: law)
References
Details
Attachments
(2 files)
When downloading stuff from an HTTP (1.0) server that does not send a
Content-Length header, the download window will contain a couple of peculiarities:
Progress: ... NaN %
100 of 0 kB downloaded
Time: 0:-16
The dialog should handle this by just showing the bytes downloaded, time
elapsed, and perhaps some barber pole or similar.
Comment 1•23 years ago
|
||
Comment 2•23 years ago
|
||
could you pls provide a specific example that'd exhibit this bug? also, could
you let me know what buildid and theme you are using?
thx!
Assignee: blakeross → law
I've attached a perl script that acts as a dummy http server. Run this and
connect to http://localhost:8910/ to see the bug in action. AFAIK the response
is valid HTTP/1.1. The screenshot was taken while testing this server.
In real life this bit me while talking to the Freenet fproxy (see
http://freenetproject.org/), but testing with my dummy server is obviously much
easier than setting up a Freenet node.
BTW, this does resemble 69037, but is not at all like 61947. Hmm.
Do you see the same (or similar) results when you right-click on a link to such
content and choose "Save link as..."? Thanks.
No, the problem manifests itself only when going through the "what should
mozilla do with this file" dialog. Regardless of whether you choose to save or
launch a helper, there. "Save Link As..." brings up a slightly different
progress dialog, which behaves as expected (1 of ??kB; barber pole). All with
the modern theme.
Just retested with today's build.
Comment 10•23 years ago
|
||
*** This bug has been marked as a duplicate of 84410 ***
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
Updated•20 years ago
|
Product: Core → Mozilla Application Suite
You need to log in
before you can comment on or make changes to this bug.
Description
•