backward and forward buttons for message navigation are almost useless

RESOLVED INVALID

Status

--
enhancement
RESOLVED INVALID
12 years ago
12 years ago

People

(Reporter: a_geek, Assigned: mscott)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

12 years ago
User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-GB; rv:1.8.1.3) Gecko/20070309 Firefox/2.0.0.3
Build Identifier: 2.0.0.0 (20070326)

In TB 1.5.0.9, I can put a pair of green angle brackets on my button bar and use them to navigate through messages in a folder w/o thinking about whether I had already read a message, whether there's a new message in that folder etc.pp. This allows me to easily scroll through a list of messages w/o having to use the slider to bring the appropriate portion of the folder into the message listing pane. In TB 2.0.0.0, this no longer seems to work, and I have two sets of back/forward buttons which both don't do that, but confine navigation to messages I had already visited in that folder, or to new messages, so they're dysfunctional most of the time, and also, I most often have to use the backward button of one pair and the forward button of the other pair, which is awkward at best.

Please restore the UI to have one pair of buttons (or some config option to change behaviour) to allow navigating just one message backward or forward, no matter whether the message was already read or not.

Reproducible: Always

Steps to Reproduce:
1.
2.
3.



The current behaviour makes TB2 very clumsy to use, and is a significant step backwards compared to TB1.5.
The functionality of the existing next previous buttons (from 1.5) were not changed to my knowledge. If you don't like the history navigation buttons you can remove them by using customize toolbar (through right clicking it).

> Please restore the UI to have one pair of buttons (or some config option to
> change behaviour) to allow navigating just one message backward or forward, no
> matter whether the message was already read or not.

Those buttons never worked like that, it was always only for unread msgs.
(Reporter)

Comment 2

12 years ago
Unfortunately, I have to agree after looking at it again, so, in essence, it was a user (my) error.

Nevertheless, I'd like to see this functionality.

Is it better now to resolve this bug as invalid and open a new one as an enhancement, or is it ok to keep this as enhancement, but confirm?
->INVALID per previous discussion.

The RFE is bug 235666.

Status: UNCONFIRMED → RESOLVED
Last Resolved: 12 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.