207925 - Message Compose window cannot interpret '\n' correctly in the body argument passed from -compose commandline

Status: VERIFIED DUPLICATE of bug 208230

(MailNews Core :: Composition, defect)

Description

[Joe]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4a) Gecko/20030401
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4a) Gecko/20030401

Try the following commandline:
$mozilla -compose body="first line\nsecond line"
The launched compose window interpret '\n' to a whitespace instead of creating a
new line. I've tried to hex encoding '\n' as %0A, the problem is still there.

Reproducible: Always

Steps to Reproduce:
1.run commandline:
$mozilla -compose body="first line\nsecond line"
2.
3.
Actual Results:  
the launched compose window show all the characters in one single line, '\n' is
interpreted as a whitespace 

Expected Results:  
interpret '\n' correctly.

The same problem could also be produced when using MozMapi API, say, if we
create a MapiMessage object, whose body contains '\n', when the compose window
was launched, '\n' cannot be interpreted correctly either.

However the mailto URL handler can accept %0A. try this:
$mozilla "mailto:?body=first line%0Asecond line"
it seems to work well.

-compose and MozMapi should also accept multilines bodys.

Comment 1

[Jason M. Abels]

Verified, but that's because DOS doesn't see \n as an escaped character.

This works if you replace \n with %0A in the testcase provided. However, I think
the command-line interpreter should do this for you.

Comment 2

[Joe]

sorry I made some mistakes so that I filed the same bug twice. there is another
bug #208230, they are exactly the same. 

*** This bug has been marked as a duplicate of 208230 ***

Comment 3

[Jason M. Abels]

verifying and removing my CC