Activity doesn't stop on next local msg selection after delete

VERIFIED FIXED

Status

P3
normal
VERIFIED FIXED
19 years ago
10 years ago

People

(Reporter: laurel, Assigned: scottputterman)

Tracking

Trunk
x86
Windows NT

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

19 years ago
Using 2000-03-10-09m15 commercial build NT 4.0
Don't see in yesterday's linux and mac builds, today's builds not out yet 

The acitivity progress bar and throbber never stop for next message selection
after deleting a message in local folder when the message pane is closed.

1.  Launch to mail window, go to local folders.
2.  Select a folder with several messages in it (top level folder or subfolder).
3.  With message pane open, select a message and wait for contents to finish
loading.  All activity indicators stop.
4.  Delete this message. Next message is selected and downloaded, activity
indicators stop. All is fine.
5.  Click the grabber which snaps the message pane closed.
6.  Delete the message.

Result:  Message is deleted, next message is selected. However the throbber and
barber pole progress indicator continue to stay active -- doesn't ever stop.

Notes:  
1.  Every once in awhile I see this work okay.  But if you repeat a couple times
it'll fail.
2.  Stop does not stop the activity indicators.
3.  Opening the thread pane will indeed load the correct message content,
activity will stop --> Document Done.
(Reporter)

Updated

19 years ago
QA Contact: lchiang → laurel
(Reporter)

Comment 1

19 years ago
win32 only
(Reporter)

Updated

19 years ago
Summary: Acitivity doesn't stop on next local msg selection after delete → Activity doesn't stop on next local msg selection after delete
(Assignee)

Comment 2

19 years ago
fix checked in.
Status: NEW → RESOLVED
Last Resolved: 19 years ago
Resolution: --- → FIXED
(Reporter)

Comment 3

19 years ago
OK using 2000-03-27-09m15 commercial build NT 4.0
Status: RESOLVED → VERIFIED
Product: MailNews → Core
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.