Bill Law Assignee
	Description • 25 years ago

Must defer till M9; this really needs to await Necko since it will be
imposing substantive changes in this area.

	don Reporter
	Comment 1 • 25 years ago

Move this to M10.

	Claudius Gayle
	Comment 2 • 25 years ago

is there any status/progress on this?

	Bill Law Assignee
	Comment 3 • 25 years ago

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.

	leger
	Comment 4 • 25 years ago

Putting on PDT+/Dogfood radar.

	don Reporter
	Comment 5 • 25 years ago

Bill says he may be able to bring this in to 11/26.

	Jim Roskind
	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.

	don Reporter
	Comment 7 • 25 years ago

OK, moving out to M13.

	don Reporter
	Comment 8 • 25 years ago

Move to M14.

	don Reporter
	Comment 9 • 25 years ago

Ooops.  Should be M13.

	don Reporter
	Comment 10 • 25 years ago

*** Bug 22973 has been marked as a duplicate of this bug. ***

	sairuh (rarely reading bugmail)
	Comment 11 • 25 years ago

spam: added self to cc list.

	Paul MacQuiddy
	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.

	Bill Law 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").

	Paul MacQuiddy
	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?

	don Reporter
	Comment 15 • 25 years ago

Added dependency on bug #13374, Travis' webshell work.

	Bill Law 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.

	don Reporter
	Comment 17 • 25 years ago

*** Bug 20972 has been marked as a duplicate of this bug. ***

	don 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.

	Tomi Leppikangas
	Comment 19 • 25 years ago

Just FYI, bug #18724 handles mostly this same thing. Should this depend on
it?

	don Reporter
	Comment 20 • 25 years ago

Move to M16 ...

	leger
	Comment 21 • 25 years ago

Putting on [nsbeta2-] radar. Not critical to beta2.

	don Reporter
	Comment 22 • 25 years ago

Move to M20 target milestone.

	sairuh (rarely reading bugmail)
	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. :-)

	verah (gone)
	Comment 24 • 24 years ago

Nav triage team: [nsbeta3+]; look at Don's 2/01 comment

	Daniel Veditz [:dveditz]
	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.

	Bill Law 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.

	Claudius Gayle
	Comment 27 • 24 years ago

marking VERIFIED Fixed with 2000082108 builds (note there exist other, documented bugs)