Closed Bug 115380 Opened 24 years ago Closed 24 years ago

Thread pane shows no msgs after a few msgs have been moved into the folder

Categories

(MailNews Core :: Backend, defect, P2)

All
Windows NT
defect

Tracking

(Not tracked)

VERIFIED DUPLICATE of bug 119404

People

(Reporter: cavin, Assigned: naving)

References

Details

BuildID: 20001121403 I moved some msgs from imap folder 'a' to imap folder 'b' and then clicked on folder 'b' to read those msgs again. Then, an empty thread pane showed up after the folder was opened. I had to click on some other folder (imap or local) and then back to 'b' to see the msgs. One way I know to consistently reproduce this is the following although I'm not sure if folder 'b' I mentioned above was empty before I moved msgs into it: 1. Log into an imap acct (so INBOX is opened in thread pane). 2. Create a new imap folder 'Test1' and then select and move some (1 or more) msgs into this new folder. Note that NO NOT open 'Test1' before moving msgs into it. 3. Now open folder 'Test1'. After the folder is opened, no msgs will show up in the thread pane.
Don't know about the move messages case, but there's some general weirdness happening with switching folders/groups -- see bug 115381.
QA Contact: esther → sheelar
Blocks: 113421
reassigning to naving. I was able to reproduce this following Cavin's steps.
Assignee: mscott → naving
Keywords: nsbeta1
Status: NEW → ASSIGNED
Keywords: nsbeta1nsbeta1+
Priority: -- → P2
I think bienvenu might have fixed this and it is checked in. cavin, can you try again?
Running 01/22/2002 commercial build and it does seem to work find. David, do you remember how you fixed it?
Sorry for the typo: work find --> work fine.
*** This bug has been marked as a duplicate of 119404 ***
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → DUPLICATE
No longer blocks: 113421
Cavin, see bug 119404 for all the gory details.
vrfy dup
Status: RESOLVED → VERIFIED
Product: MailNews → Core
Product: Core → MailNews Core
Blocks: 1141493
You need to log in before you can comment on or make changes to this bug.