Closed Bug 135744 Opened 22 years ago Closed 22 years ago

Message view doesn't work after replying to a message. w/mail start page set to some pages.

Categories

(SeaMonkey :: MailNews: Message Display, defect)

x86
All
defect
Not set
major

Tracking

(Not tracked)

VERIFIED DUPLICATE of bug 99496

People

(Reporter: esther, Assigned: sspitzer)

Details

Linux only, using build 20020405 if I reply or forward a message, the message
pane no longer displays currently selected messages.  If you change folders, an
select a message the pane is now blank.

1. Launch app
2. go to mail and login.
3. Select a mail message and reply to it or forward it.
4. Selelct another mail message

Result:  Currently selected mail message is not displayed in the message pane
Expected:  selecting messages should display them in the message pane.
Note, I changed profiles and the profile with only 1 account and it works OK. I
need to investigate more on why my other profile (with 7 mail accounts) is not
working.  I'll update when I find out.
Severity: critical → normal
OK, this happen on windows too and is associated with the Mail start page.
If the mail start page is http://abcnews.com or http://nbcnews.com or
http://netscape.com  (these are the only ones I tried so far) after replying or
forwarding a message the message view becomes usless.  reassigning qa me me
since this has to to with Mail Start page, thanks olga
OS: Linux → All
QA Contact: olgam → esther
Severity: normal → major
OK, this is a dup of 99496, unfortunately it's been a while since I tested Mail
Start page so I didn't remember this bug when I first saw the message window
badness.  I'm sure this will come up again.  

*** This bug has been marked as a duplicate of 99496 ***
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → DUPLICATE
Summary: Message view doesn't work after replying to a message. → Message view doesn't work after replying to a message. w/mail start page set to some pages.
verified dup
Status: RESOLVED → VERIFIED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.