Closed Bug 386051 Opened 18 years ago Closed 18 years ago

Next and Prev buttons don't work

Categories

(Thunderbird :: Mail Window Front End, defect)

x86
Windows Vista
defect
Not set
major

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: mozilla, Unassigned)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.8.1.4) Gecko/20070515 Firefox/2.0.0.4 Build Identifier: 2.0.0.4 (20070604) The previous version had next/prev buttons when viewing a message in a separate window. This enabled quick run through of all the messages. The buttons were missing from 2.0. I did add them back, but they do not appear to do anything Reproducible: Always Steps to Reproduce: 1.Double click a message to open in a separate window 2. customize the toolbar to add next/prev buttons 3. click them Actual Results: nothing happens Expected Results: expected to move to the next/prev message in the message list
They only operate on unread messages. (And if you are talking about the new back/forward buttons, those are for history.)
Version: unspecified → 2.0
Got it. It seems that the next/prev buttons should also be able to iterate through the messages in your list (not just the unread ones). Perhaps holding down a key could result in going to the next unread (or something). But without any qualification, one would expect that pressing the button would take you to the next (or previous) button...
(In reply to comment #2) > It seems that the next/prev buttons should also be able to iterate through the > messages in your list (not just the unread ones). That's bug 235666. ->INVALID, since the buttons clearly work
Status: UNCONFIRMED → RESOLVED
Closed: 18 years ago
Resolution: --- → INVALID
In version 2.0.06 I also find the next and back keys in the tool bar do not work. In previous versions they work but only for unread messages. Since downloading 2.0.06 nothing happens with the keys.
Michael: please read the bug before commenting. Next and previous are not the same as Back and Forwards.
You need to log in before you can comment on or make changes to this bug.