Closed Bug 159523 Opened 23 years ago Closed 23 years ago

Status bar information in Netscape style

Categories

(SeaMonkey :: General, enhancement)

x86
Windows 95
enhancement
Not set
normal

Tracking

(Not tracked)

VERIFIED DUPLICATE of bug 88982

People

(Reporter: andrixnet, Assigned: Matti)

Details

I respectfully request that Mozilla continue in the tradition of the Netscape browser with proper, information rich status bar messages : A page loading should display the following sequence : 1) Looking up host name [host] ... (resolver lookup) (current implementation "Resolving ..." is ok) 2) Contacting host [host] ... (SYN sent, waiting for TCP connection) 3) Connect: Host contacted, waiting for reply (TCP connection open, request headers sent) 4) overall: display progress for html page, periodically cycle progress display for inline images/embeds overall: progrogress bar should reflect the percentage displayed as text. 4a) Receiving xx% of yyykB [filename] (download progress indicator for filename) 4b) Receiving xx% of yyykB (ETA: mm:ss; rate: zzkb/s) [filename] (download progress indicator with ETA display, activated after allowing sufficient time for initial statistics to be gathered) 4c) Receiving yyykB [filename] (download progress, no filesize available in response headers) 4d) Receiving yyykB (rate: zzkB/s) [filename] (download progress, no filesize available in response headers, transfer rate estimator display) 5) Document done. (page has finished loading) ------------------------ Current behaviour: step 1) Resolving host... step 2+3) Sending request... (offeres less information) step 4) Transfering data from ... (offeres much less information then Netscape 3/4, no usable progress, etc, progress bar on the right leaves the user to wander to what exactly it refers...)
Whiteboard: DUPEME
*** This bug has been marked as a duplicate of 88982 ***
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
Verified.
Status: RESOLVED → VERIFIED
-DUPEME
Whiteboard: DUPEME
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.