72301 - Status bar not updated often enough.

Status: RESOLVED DUPLICATE of bug 131256

(SeaMonkey :: UI Design, defect)

Description

[Ben Bucksch (:BenB)]

From bug 62976:
What are those 400ms? The frequency in which the status bar is updated? Then,
this seems indeed to slow to me, 100ms would be more appropriate IMO, unless it
creates a noticable slowdown.

Comment 1

[Peter "jag" Annema]

John, got some time to investigate this?

Comment 2

[John Morrison]

Um, maybe. It would be interesting to at least get a 200msec run in, and 
see what it hints at. In the end, we can tune this just before 1.0, since
aside from perf. issues, changing the interval would not have other side
effects (famous last words).

Comment 3

[selmer (gone)]

nom nscatfood, feedback mechanisms are a top user comment.  

Can we get the data posted in this bug?  What happens when we use 100ms and 200ms?

Comment 4

[Peter "jag" Annema]

Mass move to [e-mail]

Comment 5

[Peter Trudelle]

->0.9.3, good limbo candidate

Comment 6

[saari (gone)]

->0.9.5 going to jrgm

Comment 7

[John Morrison]

I suck -> 0.9.6

Comment 8

[John Morrison]

darin may have already fixed this. need to check. soon. really.

Comment 9

[John Morrison]

.

Comment 10

[John Morrison]

.

Comment 11

[Ben Bucksch (:BenB)]

Nominating for 1.0. Updating every 400ms is not fast enough (will miss some
information). Trivial change.

Comment 12

[Andreas Kunz]

Those 400 ms did a long journey since this bug was fixed:
They were removed from navigator.js with revision 1.322.
http://bugzilla.mozilla.org/attachment.cgi?id=30055&action=view (from bug 46200)
moved them into nsBrowserStatusHandler.js on 04/14/2001.

On Aug 06 2002 they were moved to
http://lxr.mozilla.org/seamonkey/source/xpfe/browser/src/nsBrowserStatusFilter.cpp#292
with patch http://bugzilla.mozilla.org/attachment.cgi?id=93338&action=view of
bug 144533.

What does this comment want to say? Originally that those 400 ms have
disappeared or changed, but since they moved I want to let you know so you don't
have to do this search for yourself...

Comment 13

[Andreas Kunz]

This seems to have been fixed with
http://bugzilla.mozilla.org/attachment.cgi?id=108800&action=view
which was checked in for bug 131256.
(See my previous comment for how this fix exactly addresses this bug.)
However, that other bug is not yet closed (pageload time issues), so maybe it's
too early to resolve this one here.
Should this bug depend on that one or something?

Comment 14

[Andreas Kunz]

Bug 131256 really fixed this (checkin comment: "Bug 131256: make status bar
reflect actual activity, lower time between status updates from 400ms to 40ms.").
-> duplicate (after conversation with reporter)

Please reopen if anybody still has something in mind with this bug...

*** This bug has been marked as a duplicate of 131256 ***