After second carriage return, spaces in second line are gone or replaced with strange characters. Reproduced on: Win32 6/2 build Mac 6/2 build Linux 6/2 build Was not a problem in the M6 builds. First seen on html mail compose, but reproduced on the editor. 1) In the editor, type: this is line 1 2) Press enter/return 3) Type: this is line 2 4) Press enter/return 5) Results: a) On Win32, the spaces on line 2 is lost. You see: thisisline2 b) On Mac, you get a strange square-ish type of character in place of the spaces. c) On Linux, you get a Chinese character in place of the spaces. I don't know if this is related to bug 7470 (6896). Those bugs don't mention the <enter/return> keys and this problem was not seen in M6. Pls fix this for M7. Hard to use mail on a "real basis" without being able to enter new lines :-) Thanks.

assigned to Joe, looks like the typing rules have gone whacky.

Update to this bug: after you correct the spacing and continue to type and then send the message, text you typed is not received except for the first word. chofmann entered this in bug http://bugzilla.mozilla.org/show_bug.cgi?id=7599 Is the sending part a separate bug? scott?

Lisa, the send part is already reported into the bug about putting two space between words that truncated the output text. I don't remember the bug number, it was from last week I thing and has been reassign to Ender folk.

Jean-Francois, from your comments, I take it there isn't a mailnews send problem here? But the data was truncated when putting the spaces there by ender right?

<For the record, the send bug Jean-Francois is referring to is http://bugzilla.mozilla.org/show_bug.cgi?id=7479>

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

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

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

All these bugs can be yours! Act now! dup of 7479 *** This bug has been marked as a duplicate of 7479 ***

verified in 6/8 build.

Sujay - leaf has not announced any builds for 6/8 yet (it's 10am now). How did you verify in the 6/8 build that this is working? Or did you verify that it is a duplicate? Thanks

I just verified that its a DUP....I figure the other bug will be regressed...

Bug 7479 which this bug is marked a dup of was marked fixed yesterday. So, in today's builds (6/8), you should be able to verify this fix in the composer.

okay it works now...verified in 6/8 windows build...