Sykje yn Support

Mij stipescams. Wy sille jo nea freegje in telefoannûmer te beljen, der in sms nei ta te stjoeren of persoanlike gegevens te dielen. Meld fertochte aktiviteit mei de opsje ‘Misbrûk melde’.

Mear ynfo

Dizze konversaasje is argivearre. Stel in nije fraach as jo help nedich hawwe.

Gmail: move to next message after marking message as deleted

  • 1 antwurd
  • 1 hat dit probleem
  • 2 werjeftes
  • Lêste antwurd fan Toad-Hall

more options

I use Gmail on Thunderbird and . I love it. Gmail GSuite/Business Suite. I like to open a new email message on a new window. After pressing "delete" the email message is marked as "deleted" with a line crossing the email out in the list. But the message window does not advance to the next message!!! Can you enable this? I have to press "F" to advance to next message. Thanks.

I use Gmail on Thunderbird and . I love it. Gmail GSuite/Business Suite. I like to open a new email message on a new window. After pressing "delete" the email message is marked as "deleted" with a line crossing the email out in the list. But the message window does not advance to the next message!!! Can you enable this? I have to press "F" to advance to next message. Thanks.

Alle antwurden (1)

more options

I've got a gmail account and altered the settings to be like yours as I usually use 'Move it to the gmail Trash' I also changed my double click settings from opening in tab to new window. I also selected to close window upon move or delete.

I found opening in a new window worked ok. delete marked email in list with a line. Window did not close upon delete. email selection did not auto advance

I use 'Move it to the gmail Trash' as I want deleted emails to be fully removed some server and not just a label removed. Generally I read opened emails in the Message Pane open in a new tab for double click upon delete the opened tab closes and email selection advances to show next email in Message Pane. So all works as expected for me using those settings.

Your issue sounds like this bug report: https://bugzilla.mozilla.org/show_bug.cgi?id=452394