80718 - header info displayed in body

Status: VERIFIED DUPLICATE of bug 76558

(SeaMonkey :: MailNews: Message Display, defect)

Description

[Tim Wunder]

Occasionally when viewing messages, header info is displayed in the body of the
message and formatting is lost. If you click on another message and return to
the offending message, all is once again well. I can provide screenshots, just
tell me where to send them.

This is what was displayed in the message body of one of my posts to
n.p.m.mail-news:

"Path: news.abs.net!not-for-mail Message-ID: <[e-mail]>
From: Tim Wunder User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
rv:0.9) Gecko/20010505 X-Accept-Language: en MIME-Version: 1.0 Newsgroups:
netscape.public.mozilla.mail-news Subject: Scroll from next button Content-Type:
text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit
Lines: 11 Date: Mon, 14 May 2001 10:29:01 -0400 NNTP-Posting-Host: 162.33.157.18
X-Complaints-To: [e-mail] X-Trace: news.abs.net 989850524 162.33.157.18
(Mon, 14 May 2001 10:28:44 EDT) NNTP-Posting-Date: Mon, 14 May 2001 10:28:44 EDT
Xref: news.abs.net netscape.public.mozilla.mail-news:11779 With NC 4.7x, you can
scroll the text of a mail/news message while on the Next button. This allows the
user to keep the mouse over the Next button while reading news. Clink Next,
scroll message, click next. I thought I saw someone mention a bug pertaining to
this, but can't seem to find it in Bugzilla. Anybody know of a bug on this? If
not, I'll submit one. Regards, Tim"


When I click on another message and then return, this is displayed:

"With NC 4.7x, you can scroll the text of a mail/news message while on the Next
button. This allows the user to keep the mouse over the Next button while
reading news. Clink Next, scroll message, click next.

I thought I saw someone mention a bug pertaining to this, but can't seem to find
it in Bugzilla.

Anybody know of a bug on this? If not, I'll submit one.
Regards,
Tim"

I can get a message to exhibit this problem again by clicking different messages
in rapid succession, but no definitive technique can duplicate the problem 100%.

Comment 1

[Koike Kazuhiko]

Should bug 76558 be reopened?

Comment 2

[[e-mail] (gone - use [e-mail] instead)]

Most unfortunate, but this fix (in bug 76558 wasn't checked in to the branch for 
0.9).

*** This bug has been marked as a duplicate of 76558 ***

Comment 3

[[e-mail] (gone - use [e-mail] instead)]

Use a nightly instead.