Closed Bug 161374 Opened 22 years ago Closed 15 years ago

shouldn't there be a "back" button in Mail/News toolbar?

Categories

(SeaMonkey :: MailNews: Message Display, enhancement)

enhancement
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: hao2lian.bugzilla, Unassigned)

References

()

Details

I was wondering.... shouldn't a back button be in Mail/News, for functionality and compeleteness?
I can think of absolutely no reason for a back button in mail... are there any?
Reading messages one after another creates a history that could be considered for navigation with Back/Forward buttons? Maybe a global Mail/News History window too?
Severity: trivial → enhancement
Status: UNCONFIRMED → NEW
Ever confirmed: true
OS: Windows 98 → All
Hardware: PC → All
One scenario: You read a message in a *new window* and decides it should stay in your Inbox instead of being deleted or being filed to another folder. You press next. However you want to read that previous message again. So you have to switch to the main window scroll up, and click on it again. If there was a Back button, it would make this process much easier.
It would be very useful in News in the Tree-View. There it could be useful to get back if someone has pressed the 'n'-key too much and it is not easy to find the previous viewed message.
QA Contact: olgam → laurel
Depends on bug 74959, ``implement mail "back" and "forward"´´. When this is done, it is probably a trivial task to add a button to the toolbar.
Depends on: 74959
This seems more like a dup of 74959. I think that an interface for back and forward is implied in that bug.
Thunderbird now implements this, thanks to mscott. Any future plans to copy code from that into Mozilla's Mail/News?
Product: Browser → Seamonkey
Assignee: sspitzer → mail
Assignee: mail → nobody
QA Contact: laurel → message-display
MASS-CHANGE: This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state. If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way. If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar). If no action happens within the next few months, we move this bug report to an EXPIRED state. Query tag for this change: mass-UNCONFIRM-20090614
Status: NEW → UNCONFIRMED
FIXED by mnyromyr in October 2007, see bug 74959
Status: UNCONFIRMED → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.