Closed
Bug 8705
Opened 25 years ago
Closed 24 years ago
[FEATURE] Better status/progress feedback
Categories
(SeaMonkey :: UI Design, defect, P2)
SeaMonkey
UI Design
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: don, Assigned: law)
References
Details
(Whiteboard: [nsbeta2-][nsbeta3+])
Must defer till M9; this really needs to await Necko since it will be
imposing substantive changes in this area.
Updated•25 years ago
|
QA Contact: beppe → claudius
Comment 2•25 years ago
|
||
is there any status/progress on this?
Gagan has got notifications flowing so the status bar is back to where it was
pre-Necko. Still need to enhance the progress meter. May be getting a
volunteer from outside.
Summary: [FEATURE] Better status/progress feedback → [FEATURE][DOGFOOD] Better status/progress feedback
Whiteboard: [PDT+][DOGFOOD] → [PDT+]
Updated•25 years ago
|
Whiteboard: [PDT+] 12/3 completion → [PDT-] 12/3 completion
Comment 6•25 years ago
|
||
Changing to PDT- per discussion of PDT long poles. The most we could rate as
dogfood is an indication that some progress is taking place. It is not
necessary to see better percentage values etc. for dogfood.
Priority: P1 → P2
Summary: [FEATURE][DOGFOOD] Better status/progress feedback → [FEATURE] Better status/progress feedback
Whiteboard: [PDT-] 12/3 completion
Target Milestone: M13 → M14
Reporter | ||
Comment 10•25 years ago
|
||
*** Bug 22973 has been marked as a duplicate of this bug. ***
Comment 11•25 years ago
|
||
spam: added self to cc list.
Comment 12•25 years ago
|
||
Sorry to be clueless, but does this bug deal with progress bar and status in
save as dialogues or the page loading status bar at the bottom of browser
window, or both.
Assignee | ||
Comment 13•25 years ago
|
||
This bug refers to the progress meter at the bottom of the browser window. It
is supposed to switch to thermometer mode when loading big/slow pages (and the
status bar should say something like "3% of 47K at 3.2K/sec").
Comment 14•25 years ago
|
||
Good, then I'm in the right place. I was trying to verify bug 16386, which deals
with a trivial spelling error in 'transferring data' that used to appear there,
but I don't see that anymore. Is that related to this?
Reporter | ||
Comment 15•25 years ago
|
||
Added dependency on bug #13374, Travis' webshell work.
Assignee | ||
Comment 16•25 years ago
|
||
Moving out to M14 as the requisite changes to the webshell and uri loader won't
happen till post-M13.
Reporter | ||
Comment 17•25 years ago
|
||
*** Bug 20972 has been marked as a duplicate of this bug. ***
Reporter | ||
Comment 18•25 years ago
|
||
Adding this from bug #20972:
1. The progress bar message does not change at all when a new page is loaded.
During loading, it shows the "Document: Done (xx seconds)" message of the
previous page loaded; instead it should display "Contacting server", "Waiting
for reply", etc.
2. If a page load is interrupted, the progress message shows "Document: DOne (xx
seconds)" where xx seconds is the time between clicking on a link and clicking
on the stop button. This is slightly confusing, since whatever is shown in
theprogress bar should apply to the page currently viewed.
Comment 19•25 years ago
|
||
Just FYI, bug #18724 handles mostly this same thing. Should this depend on
it?
Updated•24 years ago
|
Component: XP Apps → XP Apps: GUI Features
QA Contact: claudius → sairuh
Comment 23•24 years ago
|
||
whoops, almost thought this had to do with the downloading status dialog.
chatted with claudius, who clarified things (yay) --back to him. :-)
QA Contact: sairuh → claudius
Comment 24•24 years ago
|
||
Nav triage team: [nsbeta3+]; look at Don's 2/01 comment
Whiteboard: [nsbeta2-] → [nsbeta2-][nsbeta3+]
Comment 25•24 years ago
|
||
Adding nsbeta3 keyword to bugs which already have nsbeta3 status markings so
the queries don't get all screwed up.
Keywords: nsbeta3
Assignee | ||
Comment 26•24 years ago
|
||
I'm going to resolve this FIXED. Progress/status messages are pretty good
nowadays. One sees (typically):
Resolving host <host>
Connected to <host>
Reading <url>
Document: Done
Plus, a percentage read, when applicable.
There might still be some flakiness, but those should be addressed via separate
bugs (which might already exist, for all I know); those bugs aren't likely to be
nsbeta3'ers.
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
Comment 27•24 years ago
|
||
marking VERIFIED Fixed with 2000082108 builds (note there exist other, documented bugs)
Status: RESOLVED → VERIFIED
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
•