143892 - ftp "KB/s" sticks at the start value

Status: RESOLVED WORKSFORME

(SeaMonkey :: Download & File Handling, defect)

Description

[Joachim Otahal]

When (for example) downloading from
ftp://ftp.mozilla.org/pub/mozilla/nightly/latest-1.0.0/mozilla-win32.zip Mozilla
doesn't adjust the displayed "KB/s" speed to the rise or fall of the real speed.
It always stays at the start value. When downloading http:// stuff the "KB/s"
display works as expected. The url ftp://ftp.nero.com/Nero5582.exe gives the
same effect. I didn't find any ftp link where that behaviour did not appear.

Comment 1

[Lorenzo Colitti]

I'm seeing this as well with RC2 on WinME.

The progress bar doesn't actually stick, it just updates very rarely (like once
every 30-50 seconds). The download manager window updates much more frequently.

This is a regression, although I don't know when it broke. I'm sure it was
working fine in January; I know that's little too vague...

Setting 4xp keyword as 4.x had great download progress bars.

Comment 2

[Jo Hermans]

see bug 81857

Comment 3

[Robert Kaiser]

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 4

[Joachim Otahal]

This bug was reported by me in 2002, it was (at that time) reproducible on some machines, a few month later the effect did not reappear.

So "EXPIRED" would be closer to the truth than "WORKSFORME" : ), but it doesn't make any difference in the end.