Open Bug 74432 Opened 24 years ago Updated 15 years ago

View menu has Watch/Ignore for mail, feature is news only

Categories

(SeaMonkey :: MailNews: Message Display, defect)

Product:
SeaMonkey
Component:
MailNews: Message Display
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

People

(Reporter: laurel, Unassigned)

References

Details

Using apr2 commercial trunk build The View menu has Watched Threads with Unread as an option for mail, but the underlying feature Message|Watch Thread is available only for news. We should disable the view for mail if we are not going to expose the Watch Thread feature in mail.
QA Contact: esther → fenella
Keywords: nsCatFood
QA Contact: fenella → laurel
*** Bug 95679 has been marked as a duplicate of this bug. ***
I think it would be best to enable "Thread Watching" for mail. When email messages are viewed as threads the UI should be virtually identical to newsgroups. This is best for mailing lists.
The help system does not make this clear. In "Using Mozilla Mail | Organizing Your Messages | Marking or Flagging Messages", there's a section "Monitoring Threads". It doesn't say this is only possible for mail. Also, I went to this help topic because I was unable to find the watch option anywhere in the menu, though I'd seen it before. Isn't it more appropriate to visually disable a menu option when it doesn't apply than to remove it from the menu? Otherwise I think people will spend a lot of time looking for an option which doesn't exist in that situation, as I did. Of course, I would also prefer to see this feature for mail. But if not, those other two places should be updated IMNSHO.
I agree that the feature should be available in mail for mailing lists - cc'ing Jennifer. One caveat is that we disabled the related feature, ignore thread, for mail, because people were accidentally pressing the keyboard shortcut for ignore thread and losing mail messages. We could put them both in mail, but disable the keyboard shortcut, or make mail default to showing ignored threads...
Why would people accidentally ignoring threads be a problem with mail but not news? I hypothesize that it was just reported for mail because more people / less educated people use mail than news and/or that people use mail more frequently than news. Alternative fix for that problem: add a confirmation dialog for ignore (for both media). Is there a bug for that somewhere?
people don't care/notice when news messages go missing nearly as often as they do when mail goes missing. A confirmation dialog would have people screaming, and not in joy.
Agree with Laurel that if Watch/Ignore isn't currently implemented in Mail, then the View: Messages: "Watched Threads with Unread" menu item in Mail doesn't make sense. Implementing Watch/Ignore in Mail is a separate issue.
*** Bug 148332 has been marked as a duplicate of this bug. ***
Some new mention of Watch/Ignore being implemented for mail, not sure if it will happen... just a paper trail here --> see bug 179033.
Keywords: nsCatFood → nsbeta1
Summary: View Watched Threads is available in mail, underlying feature is news only → View menu has Watch/Ignore for mail, feature is news only
Mail triage team: nsbeta1-
Keywords: nsbeta1 → nsbeta1-
Product: Browser → Seamonkey
Assignee: sspitzer → mail
Depends on: 179033
Depends on: 261223
Assignee: mail → nobody
QA Contact: laurel → message-display
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
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
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
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
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
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
It still applies and is quite a wanted feature!
Status: UNCONFIRMED → NEW
Ever confirmed: true
You need to log in before you can comment on or make changes to this bug.