Closed Bug 82769 Opened 25 years ago Closed 25 years ago

Full headers are displayed the 2nd time a message is read

Categories

(SeaMonkey :: MailNews: Message Display, defect)

Product:
SeaMonkey
Component:
MailNews: Message Display
Platform:
x86
Windows 2000
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
VERIFIED WORKSFORME

People

(Reporter: egrochowski, Assigned: sspitzer)

References

(
URL
)

Details

(Whiteboard: DUPEME?)

From Bugzilla Helper: User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9) Gecko/20010505 BuildID: 2001050515 When reading newsgroups postings with View->Message->Headers set to Normal, and you open an unread message (call it message1), open a different unread message (call it message2), then re-open the original unread message (i.e. message1). This message (message1) now incorrectly displays full headers. Reproducible: Always Steps to Reproduce: 1.Open first unread message 2.Open second unread message 3. re-open first new message --> now it displays wrong. Actual Results: It displays FULL headers, even though it should only display "normal" headers. Expected Results: Displayed only normal headers.
I've seen this behavior, but not any more in the last week. Reporter: Could you check that again with a more recent build? BTW, it is an old bug. It may have been already reported.
Whiteboard: DUPEME?
This looks like a message caching bug. A new cache for imap and news landed on 5/15 (see bug 73819) and this bug is reported using Mozilla0.9, released a week earlier. It seems the bug has been most probably solved by that landing.
I just downloaded and installed Build 2001052304 and confirmed that the problem has indeed gone away for me. (I did a search before the my original post but could not find the related entry). Sorry for wasting your time!
Actually I feel stupid that I have not filed this bug (when it existed). It was so obvious I was sure it must have been reported by someone. I'll confirm the bug existence and then mark it FIXED. It deserves it, because the problem was real.
Status: UNCONFIRMED → NEW
Ever confirmed: true
On my own bservations as well as the reporter's comments marking WORKSFORME Problem most probably solved by the 5/15 imap and news cache landing.
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → WORKSFORME
this was the old cache bug, which has been fixed for a while.
Status: RESOLVED → VERIFIED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.