Closed Bug 289870 Opened 20 years ago Closed 20 years ago

when forwarding message with "as inline" no text is shown in new mail window

Categories

(SeaMonkey :: MailNews: Message Display, defect)

1.7 Branch
Sun
Solaris
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: aschroe1, Unassigned)

Details

User-Agent:       Mozilla/5.0 (X11; U; SunOS sun4u; de-AT; rv:1.7.5) Gecko/20041221
Build Identifier: Mozilla/5.0 (X11; U; SunOS sun4u; de-AT; rv:1.7.6) Gecko/20050322

when forwarding message with "as inline" no text is shown in new mail window
and no text is sent when pressing button send.
when forwarding with "as attachment" the original message text appears in new
mail window

Reproducible: Always

Steps to Reproduce:
1.open a message in mail client
2.forward message "as inline"
3.new mail window opens, but no forwarded text is shown

Actual Results:  
forwarded text isn't shown in the new mail window

Expected Results:  
forwarded text should be shown in the new mail window

in  Mozilla/5.0 (X11; U; SunOS sun4u; de-AT; rv:1.7.5) Gecko/20041221
it works as expected.
Version: unspecified → 1.7 Branch
Assignee: sspitzer → mail
I've tried to re-produce this problem in Mozilla 1.7.7 on Solaris and the
problem does'nt exist. Can you indicate where you got your build of Mozilla, if
you compiled it yourself can you indicate what the compiler was and what build
options you used.

Can you try closing Mozilla and then removing the 'chrome' directory and the
'XUL.mfasl' file in your Mozilla profile directory to see if it corrects the
problem.
I use the build 1.7.6 from mozilla.org.
Mozilla/5.0 (X11; U; SunOS sun4u; de-AT; rv:1.7.6) Gecko/20050322
I've tried your proposals before you wrote me, same effect as described in the
bugmail.
I have deleted the $HOME/.mozilla-dir,  changed the preferences, with/without
locking
with   xxx.cfg  -> no changes

After rebooting the machine I think,but I'm not sure, the problem isn't there
and I can't reproduce it anywhere. Dont't know why.
I think, the problem is solved, I hope.
I'll updagrade to 1.7.7 as soon as possible and hope the problem doesn't come back.

Thank you very much for your support 
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.