Open Bug 169946 Opened 22 years ago Updated 12 years ago

Mark All Read should only work on visible messages in views (such as Watched)

Categories

(SeaMonkey :: MailNews: Message Display, defect)

defect
Not set
normal

Tracking

(Not tracked)

People

(Reporter: laurel, Unassigned)

References

(Blocks 1 open bug)

Details

Spinoff of bug 169372 Mark All Read should work only on visible messages in the view. A change is coming down the pike for this to be changed/remedied in the QuickSearch view (bug 169372), but views other than QuickSearch will need separate fix. Current behavior: 1. Newsgroup has unread messages, some of the unread are in Watched threads. 2. Switch view to Watched Threads with Unread. 3. Ctrl+Shift+C or Mark All Read. Current result: All messages in the group, whether in the Watched view or not, are marked read. Suggested result: Only the messages in the Watched view would be marked read.
QA Contact: olgam → laurel
I like to Shift+Cmd+C to clear the unread count after looking through a 'group when bug 192903 has bitten. But I guess we ought to have three commands here: - Mark Newsgroup Read - clear the unread count, including any headers not downloaded but included in the current message count - Mark All Read - mark all downloaded headers in the 'group as read (would need a new name to prevent confusion and consequential dataloss, and could do with a new shortcut key) - Mark Visible Read
The way this currently works is it marks all messages in a folder read. Not just the visable messages. This is a problem is when you have a folder with thousands of messages in it it puts a heavy load on the server trying to process all those messages.
Product: Browser → Seamonkey
Assignee: sspitzer → mail
Why should it communicate with the server at all in order to mark messages as read?
for imap, messages are marked read on the server.
Blocks: mailviews
Assignee: mail → nobody
QA Contact: laurel → message-display
In thunderbird maill and news, this operates only on messages in the view/thread pane. Is it not the same for Seamonkey?
You need to log in before you can comment on or make changes to this bug.