185652 - Deleting a message when in descending (reverse) order highlights the wrong "next" message.

Status: RESOLVED DUPLICATE of bug 349763

(SeaMonkey :: MailNews: Message Display, enhancement)

Description

[Josh Emmons]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3a) Gecko/20021212
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3a) Gecko/20021212

When messages are sorted by date in decending order (that is, the most recent at
the top and the oldest on the bottom, or "anti-pine") pressing delete on a
message  will delete it and select the message that was immediately below it. 
The message immediately below it is not the "next" message because it is OLDER.
  This makes me now pres my up arrow to read the next letter.  If I want to
delete a string of my new messages, I have to press delete, up, delte, up,
delete up, etc. Mozilla should select the (newer) message above the one deleted
when messages are sorted in descending order -- or at very least provide the
options to specify which message to highlight after a delete.

See OS X's Mail.app for an example of how this should work.

Reproducible: Always

Steps to Reproduce:
1. sort mail by date in descending order
2. delete a message


Actual Results:  
the previous (read: older) message below the deleted message is now selected.

Expected Results:  
the next (read: newer) message above the deleted message should be selected.

Comment 1

[laurel]

yep, we always move downward in the threadpane list, not to newest when deleting
(unless you've deleted from the bottom).

Comment 2

[R.K.Aa.]

Resembles bug 89394

Comment 3

[R.K.Aa.]

*** Bug 195514 has been marked as a duplicate of this bug. ***

Comment 4

[Tuukka Tolvanen (sp3000)]

*** Bug 236938 has been marked as a duplicate of this bug. ***

Comment 5

[Mike Cowperthwaite]

See bug 229220 comment 1 for why this shouldn't be an absolute thing.
Bug 19625 is about a preference to control this movement.  Fixing that bug would 
fix this bug without breaking the current behavior for those who prefer it.

Comment 6

[Wayne Mery (:wsmwk)]

*** Bug 206837 has been marked as a duplicate of this bug. ***

Comment 7

[Mike Cowperthwaite]

Fixed at the dupe!  For SM 1.1/TB 2.0 [1.8.1 branch]
If you want the behavior described here, you'll need to set a hidden pref, but it's available.

*** This bug has been marked as a duplicate of 349763 ***