Closed
Bug 156585
Opened 24 years ago
Closed 24 years ago
Choosing Forward Inline as default forward in Prefs doesn't work
Categories
(MailNews Core :: Composition, defect)
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: scottputterman, Assigned: vparthas)
Details
(Whiteboard: [adt1 rtm])
Using 7/8 Win XP build.
This could be an NS only bug but I'm not sure. In NS, the default is Forward
Inline. This means that my prefs are set to have the Forward button act as
forward inline.
Here are the steps for the bug
1. Make sure Forward Inline is the default forward (in NS builds this is the
default).
2. Forward a message using the forward button.
Result: Message comes up as Forward as attachment
Expected: Message should come up as Forward inline.
I see this problem in my ns debug build but not in my mozilla build. Looking
into it.
Comment 2•24 years ago
|
||
varada is looking into it. I will take a look at it as soon I have a ns build
ready...
If I back out caillon's changes from http://bugscape/show_bug.cgi?id=12079 then
forwarding inline works.
Comment 5•24 years ago
|
||
that's very strange! we need to figure out why...
appearently undoing the net2phone patch also fixes
http://bugscape.netscape.com/show_bug.cgi?id=17548
Comment 7•24 years ago
|
||
Correction: bugscape bug 12079 was me, not caillon. Experimenting now with
selectively backing parts of it out.
Comment 8•24 years ago
|
||
I have a fix for this in http://bugscape.netscape.com/show_bug.cgi?id=17548
patch checked in to both ns trunk and ns branch.
Comment 10•24 years ago
|
||
Verified this on the 7/16 Branch on WinXP,Win2K,Mac9.1. Tested Forward with Pref
set both ways (Inline and As Attachment), the pref is respected in both
scenarios. Also tested overriding the pref using Message|Forward As... This is
working as well. Marking as VERIFIED, changing keyword to verified1.0.1
Status: RESOLVED → VERIFIED
Keywords: fixed1.0.1 → verified1.0.1
Updated•21 years ago
|
Product: MailNews → Core
Updated•18 years ago
|
Product: Core → MailNews Core
You need to log in
before you can comment on or make changes to this bug.
Description
•