Delete message with "Grouped by sort" enabled does not switch to next message

NEW
Unassigned

Status

--
minor
8 years ago
2 years ago

People

(Reporter: laxmozilla, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

8 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.14) Gecko/20110207 Firefox/3.6.14
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.14) Gecko/20110207 Lightning/1.0b2 Thunderbird/3.1.8

Just an annoying UI issue. When "Grouped by Sort" is chosen in an IMAP setting, the email list of a folder will show all emails and a breaking section for the sort. If you delete  an email, it will switch to the next message. However, once we reach the last message of a group, the cursor highlights the Grouping line instead of the next message (i.e. 'Yesterday' or 'Last Week'). It makes it hard to read messages and delete as you go.

Reproducible: Always

Steps to Reproduce:
1. Switch to "Group by Sort"
2. Select a section.
3. Click delete until you finish the current grouping
Actual Results:  
'Yesterday' is highlighted, requiring a mouse or keyboard action

Expected Results:  
Switch to first message of next group
(Reporter)

Comment 1

8 years ago
Additional update:
This happens when server settings is set to:
"Just mark as deleted" (that's how I use it). Works correctly when the message is removed immediately.
I have this same behavior (I'm on pop3) when I select both the messages and the group label! 
For example: I have this situation on messages list:

*TODAY*
message1
message2
message3
*LAST WEEK*
message4
message5

When I select the rows from TODAY to message3, and then hit delete, the new selected row is "LAST WEEK".
When I select the rows from message1 to message3 and then hit delete, the new selected row is message4 as aspected.

Mozilla/5.0 (Windows NT 6.1; rv:2.0b13pre) Gecko/20110227 Thunderbird/3.3a3pre
I forgot to mark as New
Status: UNCONFIRMED → NEW
Ever confirmed: true
You need to log in before you can comment on or make changes to this bug.