Avatar for Username

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

Echekwara usoro a. Biko jụọ ajụjụ ọhụrụ ma ọ bụrụ na ị chọrọ enyemaka.

How do I move to the next email message when I have an email open and I just want to stay on the message pane I am on (i.e., do not close the message pane)?

  • 2
  • 1 nwere nsogbu anwere nsogbu a
  • 1 view
  • Nzaghachi ikpeazụ nke Johno37

Johno37
Johno37
more options

v 52.8.0 (32 bit) - How do I move to the next email message when I have an email open and I just want to stay on the message pane I am on (i.e., do not close the message pane to return to the Inbox), and simply move to the next (read or unread) message? I do not see any option to go BACK (to the PREVIOUS) or FORWARD (to the NEXT) email? Are these buttons available for use within the message pane, and I am just not seeing them?

Otherwise, it seems I have to close the message pane, which returns me to the Inbox pane (or whatever "box" I was in), and then I have to click to open the NEXT email.

On the Inbox pane, however, there are options to customize and add buttons to the Menu Bar for Back, Forward, Next, etc. (or use key combinations: Go > Next....), but this is irrelevant (and fails to work) when I want to stay on the open message pane and move to the Next or Prior (Un)Open message.

It seems there may have been a solution to prior versions... https://support.mozilla.org/en-US/questions/1162922#answer-974997

Thanks in advance!

v 52.8.0 (32 bit) - How do I move to the next email message when I have an email open and I just want to stay on the message pane I am on (i.e., do not close the message pane to return to the Inbox), and simply move to the next (read or unread) message? I do not see any option to go BACK (to the PREVIOUS) or FORWARD (to the NEXT) email? Are these buttons available for use within the message pane, and I am just not seeing them? Otherwise, it seems I have to close the message pane, which returns me to the Inbox pane (or whatever "box" I was in), and then I have to click to open the NEXT email. On the Inbox pane, however, there are options to customize and add buttons to the Menu Bar for Back, Forward, Next, etc. (or use key combinations: Go > Next....), but this is irrelevant (and fails to work) when I want to stay on the open message pane and move to the Next or Prior (Un)Open message. It seems there may have been a solution to prior versions... https://support.mozilla.org/en-US/questions/1162922#answer-974997 Thanks in advance!

Asịsa ahọpụtara

Thanks. Running in Safe Mode restored the functionality of the Go > Next / Previous in the Message Pane and Tab.

Looking through my Add-ons more closely, I disabled Thunderbird Conversations (2.13.4 from 11/2017). This is the source of the dysfunction. Reading the FAQ on this Add-on, there is an issue which appeared in 2011 (#393) the developer has been struggling with, but there does not seem to be a 100% solution and release. I;ll follow-up with the Developer to see if they have a patch or alternative.

Thanks again.

Gụọ azịza a na nghọta 👍 0

All Replies (2)

sfhowes
sfhowes
  • Top 10 Contributor
more options

The advice in the link you cited still works, even if the focus is on the Message Pane (F8 to toggle the pane on and off). There are no forward/back/next unread/previous unread buttons for the Message Pane because those buttons belong on the Mail Toolbar.

If the F and B keys aren't working for you, there may be a broken layout or add-on causing the problem. Run in safe mode (Help/Restart with Add-ons Disabled) to check.

Johno37
Johno37 Jụọ onye nwe ya ajụjụ
more options

Asịsa Ahọpụtara

Thanks. Running in Safe Mode restored the functionality of the Go > Next / Previous in the Message Pane and Tab.

Looking through my Add-ons more closely, I disabled Thunderbird Conversations (2.13.4 from 11/2017). This is the source of the dysfunction. Reading the FAQ on this Add-on, there is an issue which appeared in 2011 (#393) the developer has been struggling with, but there does not seem to be a 100% solution and release. I;ll follow-up with the Developer to see if they have a patch or alternative.

Thanks again.