212977 - Composing wrap value does not work.

Status: RESOLVED INVALID

(MailNews Core :: Composition, defect)

Description

[Ivan Gyurdiev]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.5a) Gecko/20030715 Mozilla Firebird/0.6
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.5a) Gecko/20030715 Mozilla Firebird/0.6

Wordwrap is set at 72 chars, but takes no effect when composing plain text
messages. 

This is Thunderbird, built on Jul. 16. (nightly build)
Mozilla 1.5a, Copyright (c) 2003 mozilla.org, build 2003070823


Reproducible: Always

Steps to Reproduce:

Comment 1

[Mitch]

Works fine for me on Linux with the same cvs build as you.

Don't forget that doing  a line of 72 consequitive characters
will not split the line. You MUST have spaces in your text since
it will only split at word boundaries.

Comment 2

[Ivan Gyurdiev]

You were right, wordwrap does work if spaces are left.
However, when I receive a message from myself it's no longer wrapped at ch 72.
Perhaps I am expecting the wrong thing to happen, since mozilla 1.4 does exactly
the same. My expectation is that the wordwrap will not merely work when
composing,but that the message will look as the same way when delivered too.

Am I incorrect to expect this, or is this a bug?

Comment 3

[Illtud Daniel]

I'm using 1.4 on NT4 SP6a and I get the same behaviour, which I consider a bug,
and a rather serious one.

Behaviour: compose plain text message to self. It wraps in the composition
window at 72 chars, but the message that gets to me isn't wrapped at all. This
*shouldn't * be, IMHO. This is an easily confirmed bug - can somebody just *try*
it??

Comment 4

[Mike Cowperthwaite]

By default, Mozilla creates plain-text messages with "format=flowed" which 
allows the displayed text to be reflowed by a supporting mail client.  See bug 
168420 for information about f=f, including the informative FAQ attached to that 
bug; information is there for turning f=f off, if considered undesirable.

However, the program is working as designed; marking bug Invalid.

Comment 5

[Mike Cowperthwaite]

*** Bug 215131 has been marked as a duplicate of this bug. ***

Comment 6

[Mike Cowperthwaite]

(Dupe was incorrect; sorry.)