125625 - IMAP: Deleting multiple messages selects last message

Status: VERIFIED FIXED

(SeaMonkey :: MailNews: Message Display, defect)

Description

[Brad D. Wade]

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.8) Gecko/20020204
BuildID:    2002020406

When using Mail and News with an IMAP mail server, deleting multiple email
messages causes Mail and News to select the last message in the window pane. 
This occurs whether I use the 'Delete' key, use the menu at top, or use the
right-click menu to delete the messages, and is not specific to any email
folder.  I'm using Windows 2000 with service pack 2 and all the latest updates
from MS.  It seems that Mail and News should select the next message which is
not deleted.

I have not verified this with POP3.

Reproducible: Always
Steps to Reproduce:
1. Setup an email account with an IMAP server, with "When I delete a message:
Mark it as deleted" in the Server Settings.
2. Select two or more messages.
3. Delete the selected messages.


Actual Results:  The client program selects the last message in the message pane.

Expected Results:  It should, IMHO, select the next message that's not deleted,
like Netscape Communicator 4.x.

IMAP Server Settings (under Mail & Newsgroups Account Settings):
Checked options:
-Check for new mail at startup
-When I delete a message: Mark it as deleted

Comment 1

[Brad D. Wade]

This was broken in 0.9.8 (at least for win2k and winnt 4.0).  It's now fixed in
0.9.9, apparently with the other IMAP fixes.  Marking as FIXED.

Comment 2

[esther]

Using build 20020325 on winxp, mac 9.1 and linux and the original scenario,
multiple select and delete marks the messages delete however it doesn't select
the next message.  It just stays in that state with a blank message pane and the
selected messages still selected bug marked for deletion.  So this isn't
compelely fixed, however there are many bugs regarding what should happen after
a multiple selection of messages are deleted using the imap delete model (like
bug 79998) so I will verify this for the original scenario is fixed.