263877 - Want option to move message selection up after deleting current message

Status: RESOLVED DUPLICATE of bug 349763

(Thunderbird :: Mail Window Front End, enhancement)

Description

[Jeff Wofford]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7) Gecko/20040616
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7) Gecko/20040616

I typically sort my messages in reverse chronological order (newest messages at
the top). Whenever I delete a message, currently Thunderbird moves the selection
"down" after deleting, so that the next oldest message is selected rather than
the next newest message. Believe it or not, this simple behavior causes me to
pile up messages rather than consistently deleting them. Outlook had the option
to move the selection up or down after deletion, and I was able to configure it
"correctly", so that it was easy for me to browse-and-delete messages effortlessly.

Reproducible: Always
Steps to Reproduce:
1. Allow a group of new messages to accrue in your inbox.
2. Sort your inbox in reverse chronological order (newest at the top).
3. Select the "lowest" (oldest) new message in the list of messages.
4. Read it in the preview pane. Hit the delete button to delete it.

Actual Results:  
The currently selected message is now the next "oldest", previously read message.

Expected Results:  
Selected the next "newest" message, which in this case would be an unread message.

If you think about it, this is actually a pretty signficant workflow refinement
for those who sort in reverse chronological order. It allows you to read through
all your new messages, deleting or preserving them as desired, with no mouse
clicking and just one button press per message: delete or up. The current
implementation requires several clicks/presses per message, with older messages
constantly being unnecessarily revisited.

Comment 1

[Mike Cowperthwaite]

Seamonkey bug 19625.

Comment 2

[Ivan Ičin]

I used to look messages in the reverse chronological order, and it is really
painful with this bug. I think it is a bug, it is not an enhancment.

Comment 3

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 4

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.