Closed Bug 105052 Opened 24 years ago Closed 23 years ago

View setting "Threads with unread"

Categories

(MailNews Core :: Filters, defect)

x86
Windows 98
defect
Not set
normal

Tracking

(Not tracked)

VERIFIED DUPLICATE of bug 108906

People

(Reporter: junk, Assigned: naving)

Details

Even though View setting is set for "Threads with unread", some message subjects still display. No subjects, in the thread, show as unread. Whole newsgroup can be selected "Mark newsgroup as read" and still some show.
I can confirm this. I've had this same behavior on current nightly Moz and I believe NS6.1 (separate win2000 computers) for quite some time. Relatedly, to the extent that the View, Threads with Unread behavior works, it is not applied after Mark, All; instead, you've got to check it on again even though the menu already indicates that it is the selected behavior. I haven't been able to figure a pattern that explains the threads that are left visible. It may be unexpired threads in which you've read a message but I have little confidence in that theory.
I have the same problem running on Windows NT SP6A. If you choose to display Total and Unread, the Unread count is always equal to or greater that 1, even though no threads are unread. If you unsubscribe from the group, then subscribe, and then mark all as read, the threads that had problems before no longer have a problem.
Confirm for 1.0RC1 build 2002041711 Win2K As in #1, I cannot see any pattern in appearing of this bug (last time before today I had such behaviour with 0.9.8). As in #2, unsubscribing and subscribing again fixes the problem. Though for me, 'Unread' always show that there are no unread messages (i.e. is not shown as any number). This bug happened only in newsgroup folders, and not in mail folders.
duping. *** This bug has been marked as a duplicate of 108906 ***
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
marking verified as duplicate
Status: RESOLVED → VERIFIED
Product: MailNews → Core
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.