Closed Bug 258916 Opened 20 years ago Closed 20 years ago

Threads marked as read status return to unread when collapsed/expanded.

Categories

(SeaMonkey :: MailNews: Message Display, defect)

x86
Windows XP
defect
Not set
major

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: stephend, Assigned: Bienvenu)

References

()

Details

(Keywords: regression)

Attachments

(1 file)

Build ID: 2004-09-11-05, Windows XP Seamonkey trunk, but I'm assuming this
affects Thunderbird trunk as well, and possibly Aviary branch as well, I need to
check on that.

Summary: Threads marked as read status return to unread when collapsed/expanded.

NOTE: I'm not sure when this was regressed, but I noticed that it happened even
before Neil landed his two patches for bug 93426 and bug 112833.

Steps to Reproduce:

1.  Open news://news.mozilla.org/netscape.public.mozilla.jseng
2.  Go to the thread entitled "named scope" begun on 8/20/2004 (message ID is
news://news.mozilla.org:119/mailman.1093053304.15210.mozilla-jseng@mozilla.org)
3.  Read all the messages in the thread.
4.  Collapse the thread.
5.  Expand the thread.

Expected Results:

Thread stays at 'read' status, all messages are unbolded.

Actual Results:

All messages in the thread return to 'unread' status and become bolded once again.
Another weird behavior noticed:  We still display the green 'unread thread'
down arrow icon when the thread is at all read status.
Assignee: sspitzer → bienvenu
I don't see this in my Linux build; I'll try updating my MinGW build tonight.
Neil, did you try with the specific newsgroup?  I tried using news.verizon.net
and a different newsgroup, but couldn't reproduce, however I can always
reproduce using n.p.m.jseng on news.mozilla.org ;-(
Maybe your netscape.public.mozilla.jseng.msf file is corrupt?
Okay, yeah, interesting.  There's something funky going on here.

I just tried this with the 2004-09-16-05 build on my other machine, the laptop,
and it works fine.

I'm now wondering if it has something to do with bug 256536...
Could this bug be related to the issue of showing newsgroups with unread 
messages that are not visible because they've been cancelled (bug 160963)?
xref TB bug 218994 -- that was filed under TB 0.2, which makes me wonder how 
recent this alleged "regression" might be.
I don't know how my profile got into this state, but I can no longer reproduce this.

marking wfm with build 2004-10-05-04, Windows XP seamonkey trunk.
Status: NEW → RESOLVED
Closed: 20 years ago
Resolution: --- → WORKSFORME
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: