This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Do not want next message selected after deleting/archiving

  • 6 replies
  • 3 have this problem
  • 2 views
  • Last reply by info9721

more options

Before TB115, I used a plug-in called "Deselect on Delete" that would result in no message being selected after a message was deleted or archived.

With 115, when I delete or archive a message, the next one on the list (or previous one if deleting the message at the bottom of the list) is highlighted and marked Read. This causes me to skip over the message, thinking I've already read it. Very inconvenient, can't imagine how it's not an issue to other users.

I've seen other solutions that suggest toggling F8 to hide the preview pane. However, the next message is still selected, but not marked Read. Upon toggling F8 again, the selected message is then marked Read, making this not an optimal solution.

I was tempted to revert back to an older version, but my profile is no longer compatible. Hopefully there is a fix for this.

Thanks! - Robert

Before TB115, I used a plug-in called "Deselect on Delete" that would result in no message being selected after a message was deleted or archived. With 115, when I delete or archive a message, the next one on the list (or previous one if deleting the message at the bottom of the list) is highlighted and marked Read. This causes me to skip over the message, thinking I've already read it. Very inconvenient, can't imagine how it's not an issue to other users. I've seen other solutions that suggest toggling F8 to hide the preview pane. However, the next message is still selected, but not marked Read. Upon toggling F8 again, the selected message is then marked Read, making this not an optimal solution. I was tempted to revert back to an older version, but my profile is no longer compatible. Hopefully there is a fix for this. Thanks! - Robert

All Replies (6)

more options
more options

I have this add-on set to auto-update. I went ahead and removed it, then added it hoping to get the newest version. However, it still isn't working.

more options

Yes, the latest version appears to not work.

more options

Can someone help me understand why anyone would want the next message to be selected and marked read after deleting or archiving a message? I've never seen an email program behave this way.

I feel like I must be missing something, because TB doesn't even offer the option or a toggle for this behavior, which tells me most people are fine with it.

But for me, the selecting/marking read the next message after deleting messes me up, especially when the task at hand is reading and responding to NEW messages. With the default behavior, I move to the next unread message, skipping over the *actually* unread (but marked read) message. Days later, I receive a "did you get the message I sent" email.

It seems like the user, not the program, should be declaring when a message is read.

more options

If you close the Message Pane (F8), and check 'Close message window/tab on move or delete' in Settings/General/Reading & Display, then if messages are opened in tabs or windows, the next message is not opened when the current one is moved or deleted. But the effect of the (non-working) add-on should be built in.

more options

While this is correct, it requires opening messages in a new tab or window. But the next message is still selected, although it isn't marked as read, so I guess that's a positive. It's sad that one has to do extra steps to read a message to avoid unintended consequences.

I've used the message pane for years because it is more streamlined, everything in one window. Unfortunately, this streamlining now comes with the risk of the program deciding that by deleting/archiving a message, the next message must be marked read.

Why doesn't TB give the option of no selection of a message after deleting/archiving a message?