User pref "mail.forward_message_mode" should stick with the 4.x implementation to ease the migration. Although we are not having forward as quoted mode, we should tread both 1 & 2 as forward inline.
Status: ASSIGNED → RESOLVED
Last Resolved: 20 years ago
Resolution: --- → FIXED
Treat old , mail.forward_message_mode, forward quoted(1) as inline (2). Use forward as attachment, the default if we failed on getting the pref. nsMessenger.cpp changed.
Migration keeps value as is, however 5.0 prefs UI doesn't change based on any value for the migrated pref whereas it does work to write correct value if the pref is set through 5.0 UI. Will verify this bug when bug #21219 is fixed.
Just an update: related bug #21219 was fixed and reopened; still some issues surrounding this pref in 5.0. Will still wait to verify this bug until final resolution of #21219.
I'm going to go ahead and mark this verified, although the UI is still not showing Inline after migration of a profile having "forward quoted" value 1 set for the mail.forward_message_mode. 1. 4.x profile is set to forward quoted. 2. Migrate, check prefs.js for 6.0: still value left at 1. 3. Check 6.0 ui: set to attachment. 4. Forward a message in 6.0 right after migration: forwards inline. So... in this case, the UI still doesn't show the right thing, but the right thing is done when forwarding. Marking OK using oct09 mn6 branch commercial build.
Status: RESOLVED → VERIFIED
laurel, is there a bug logged on the UI problem?
You need to log in before you can comment on or make changes to this bug.