1221178 - Option to open previous message when current message is deleted or moved

Status: RESOLVED DUPLICATE of bug 395151

(Thunderbird :: Folder and Message Lists, enhancement)

Description

[Marcus Yoo]

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:41.0) Gecko/20100101 Firefox/41.0
Build ID: 20151014143721

Steps to reproduce:

Select a message.
Hit delete to delete the message, or move (either via menu or with drag and drop) the message to different folder.



Actual results:

If the message was the last on the list, the previous message is selected.
Otherwise, it is always the next message that gets selected and displayed.


Expected results:

There should be an option so that the user has the control over this.
The options should be "always select next", "always select previous", "no auto-selection (deselect)", "select next unread", "select the last previous selection", ...

Comment 1

[Sergey]

Actual results are confirmed. But this is not a bug and feature improvements.

Comment 2

[ComputingFroggy]

I've created an extension that implements one of the options "always select previous" : https://addons.thunderbird.net/fr/thunderbird/addon/select-prev-on-delete/

Comment 4

[Timur]

Mail program like TB has basic functions of receiving/sending mail in multiple accounts.
For me who processes a lot of mails daily, this is the next important function, that is unfortunatelly missing from TB those 9 years..
Addon "Select Prev on Delete" would be great, but does not work on TB 115.18 start, it needs disable/enable each time to work, which is annoying.

Comment 6

[ComputingFroggy]

I've updated the extension: it doesn't need disable/enable each time to work any more. Enjoy. ;)

Comment 7

[Timur]

The extension is very useful and v 2.1 works with TB 128.

Jammy has TB update from 128 to 140. Release Notes says: New "Appearance" Settings UI to globally control message threading/sorting order.
Not sure if that affects this, but I would not want to find out that is does not but obsoletes the extension.

Comment 8

[Mr Beedell, Roke Julian Lockhart [:B.RJL]]

How does this not duplicate id=395151?

Comment 9

[Marcus Yoo]

It probably qualify as duplicate. Though detailed description/ask seems slightly different, both tickets are asking for the same basic functionality.
Lets see... that other ticket was opened 16 years ago (??!!), and I opened this ticket 10 years ago... I could have done a better job of searching older bug reports. But after all these years, with one or two (or more?) tickets asking for correcting this bug/feature, we only got an extension, but no updates to the core.
Well, to make it short, yeah, this should be marked as duplicate, maybe.

Comment 10

[Mr Beedell, Roke Julian Lockhart [:B.RJL]]

Thanks. I'll tentatively mark it as one, but it can always be undone.