Closed Bug 125952 Opened 20 years ago Closed 11 years ago
Go -> Next/Previous -> Unread
When doing quick ng checks, it would be nice to just be able to hit a keystroke to effect: Go -> Next/Previous -> UnreadWatchedThread to jump to the next/previous thread that I've flagged as being watched, that has new replies. Manually going into each group and effecting View->Messages->WatichedWithUnread is somewhat painful for anything but a few groups. Also, since this is likely to only involve a small(ish) subset of the total list of ng's I'm subscribed to, it would be nice if it didn't ask if I wanted to consider the *next* group after the one I'm in. That operation is fine when just browsing new messages, but not so appropriate when only touching a subset of the groups. AgentNews has this feature, and its damn handy.
> it would be nice if it didn't ask if I wanted to > consider the *next* group after the one I'm in. I think that it should ask before crossing newsgroups. You could have a "Remember this decision" checkbox, however. CONFIRMING, because it's a valid and good suggestion, assuming that there's no dup.
Status: UNCONFIRMED → NEW
Ever confirmed: true
*** Bug 125951 has been marked as a duplicate of this bug. ***
Can I extend this rfe? If so, then also useful along these lines: having MOZ change the icon of all groups to indicate the existence of such watched threads with unread messages. Just like the thread itself shows the downward green arrow, so could the newsgroups icon. sTu.
Stuart: pleaae do not "extend" RFEs. The policy is: one issue per bug. Make a new bug for your suggestion--and, if necessary, mark it as depending on this one (I don't think there's a dependency however).
Assignee: mail → nobody
QA Contact: laurel → message-display
Summary: RFE: Go -> Next/Previous -> UnreadWatchedThread → Go -> Next/Previous -> UnreadWatchedThread
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
MASS-CHANGE: This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago. Because of this, we're resolving the bug as EXPIRED. If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component. Query tag for this change: EXPIRED-20100420
Status: UNCONFIRMED → RESOLVED
Closed: 11 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.