Closed Bug 253105 Opened 20 years ago Closed 4 years ago

Show Upload status of FORM in the status bar.

Categories

(Firefox :: File Handling, enhancement, P5)

enhancement

Tracking

()

RESOLVED INVALID

People

(Reporter: linux, Unassigned)

References

(Blocks 1 open bug)

Details

(Keywords: blocked-ux)

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8a2) Gecko/20040714
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8a2) Gecko/20040714

It would be great to see in the status bar on sending a request, that how many
(kilo)bytes have been uploaded/downloaded yet at what speed, and what is the
estimated time left - or at least how many have past. Then - for e.g. - I could
estimate how long coffee-break could I take when I must upload a few megs.

Reproducible: Always
Steps to Reproduce:
Do you want a dialog like bug 243468 or do you want this in the status bar?
I would like a dialog.
Thanks for the quick reply

*** This bug has been marked as a duplicate of 243468 ***
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → DUPLICATE
(In reply to comment #1)
> Do you want a dialog like bug 243468 or do you want this in the status bar?

Definitely not! The status bar is just for this kind of information. Dialog
boxes are disturbing.

Damn, I guess I should actually read who is talking.  Sorry, about that.
Status: RESOLVED → UNCONFIRMED
Resolution: DUPLICATE → ---
Moving to the Component File Handeling like a simular bug 88982.
Assignee: general → file-handling
Status: UNCONFIRMED → NEW
Component: Browser-General → File Handling
Ever confirmed: true
QA Contact: general → ian
Hardware: PC → All
Summary: Uploaded bytes → Show Upload status of FORM in the status bar.
Assignee: file-handling → nobody
QA Contact: ian → file-handling
Product: Core → Firefox
Version: Trunk → unspecified
Blocks: status-panel
Severity: normal → S4
Status: NEW → RESOLVED
Closed: 20 years ago4 years ago
Keywords: blocked-ux
Priority: -- → P5
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.