Closed
Bug 142962
Opened 23 years ago
Closed 22 years ago
Status Bar text sometimes sticks on 'transferring...' when cache turned off
Categories
(SeaMonkey :: UI Design, defect)
Tracking
(Not tracked)
VERIFIED
WORKSFORME
People
(Reporter: pete, Assigned: samir_bugzilla)
References
Details
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0rc2)
Gecko/20020503
BuildID: 2002050306 (1.0 branch)
with Edit -> Preferences -> Advanced -> Cache -> Compare the page in the cache
to the page on the network: set to 'Never', after loading a page atleast by
clicking on a hyperlink, status bar text remains on 'transferring data from ...'
rather than 'Document: Done ...'. if I turned the cache back on the status bar
text then worked as expected, and turned it back off again it began sticking again.
I could repeat this a number of times during this session then at one point it
stopped being repeatable. I haven't had chance to investigate how to reproduce
it again
Comment 1•23 years ago
|
||
Looks like a special case of bug 133250 ... or dupe?
(can't believe I missed that in my Bugzilla search)
my case sounds reminiscant of comment #20 in bug 133250. other than that case,
this bug sounds like a special/related case of bug 133250, but not necessarily a
duplicate
Comment 3•23 years ago
|
||
WFM with 2002092408/trunk/win2k.
reporter: can you reproduce this bug with a recent build of mozilla (for
example, 1.2alpha)? if so, please comment again with details. if not, please
resolve this bug as WORKSFORME. thanks.
Comment 4•22 years ago
|
||
no response from reporter for >30 days. resolving WORKSFORME.
reporter: if you can reproduce this with a recent build of mozilla, please
reopen this bug and comment again. thanks.
Comment 5•22 years ago
|
||
doh... really doing it this time...
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → WORKSFORME
I can't repeat it either now with 1.2
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
•