If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

No message selected after archiving a message

NEW
Unassigned

Status

Thunderbird
Mail Window Front End
9 years ago
2 years ago

People

(Reporter: Matt Dudziak, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [penelope_wants])

(Reporter)

Description

9 years ago
The problem is that after you archive a message, no message is selected in the message listing. Other actions, such as deleting a message, select the 'next' message in the list after removing the current message. Suggest that the same should be true when archiving a message.

To reproduce:
- Select a message in the middle of a list of messages
- Select Message->Archive
- Message is archived
- Note no message is selected in list as expected
(Reporter)

Updated

9 years ago
Whiteboard: [penelope_wants]

Comment 1

9 years ago
Matt, can you give a few more details? IMAP vs. Local, threaded vs. flat sort, grouped, non-grouped, etc. This works fine for me. The archive function goes through the normal message move code, ultimately (sometimes it has to create a folder first, which is async in the imap case - is that involved?).
The one failure to select I do know about is bug 481346.
I had this last night. I found that:

IMAP -> Local Folders
Local Folders -> Local Folders

worked

Local Folders -> IMAP

didn't work.

Comment 4

7 years ago
"select the 'next' message in the list after removing the current message" seems to me a breach of security because it opens a message without your consent : You may not have open, on purpose, this particular message because you think it is fraudulent or contains virus...
(In reply to Mark Banner (:standard8) from comment #3)
> I had this last night. I found that:
> 
> IMAP -> Local Folders
> Local Folders -> Local Folders
> 
> worked
> 
> Local Folders -> IMAP
> 
> didn't work.

related to bug 505604?
You need to log in before you can comment on or make changes to this bug.