153807 - extra spaces added on blank lines after > in replyed email

Status: VERIFIED WORKSFORME

(MailNews Core :: Composition, defect)

Description

[u32858]

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.0) Gecko/20020605
BuildID:    2002060511

extra spaces are added on blank lines after > in replyed email

Reproducible: Always
Steps to Reproduce:
1.get html email (or maybe normal email, i dont know if messgner parses the html
verison or uses the text section)
2.reply to it
3.

Actual Results:  see on empty lines are now like ">  " with 2 spaces after >, 

Expected Results:  these 2 spaces should not be added as they are meaning less,
when ever i edit i have to delete all these 2 spaces manually

example input:

"fdfdfdfd fsfsfdf sfdsdf"
""
"sfdfsfsdfsf"

example output

"> fdfdfdfd fsfsfdf sfdsdf"
">  "
"> sfdfsfsdfsf"

Comment 1

[Pádraig Brady]

I'll add this comment as it's realted?

select some text say:

> asdfadsfas
> asdfasdfas
< asdfadsfas
> asdfasdfasd

compose a mail to yourself (I use plain text), and
paste the above into body.

The received message will come out like:

 > asdfadsfas
 > asdfasdfas
< asdfadsfas
 > asdfasdfasd

I.E. there are extra spaces before any lines that start with >

Hmm, this is not easily reproducible

Comment 2

[u32858]

Can some one confirm this as it exists

JG

Comment 3

[Olivier Miakinen]

I confirm that the behaviour noted in #1 exists, I don't remember in which
version of Mozilla I noticed it (I have Mozilla at home and Netscape at work,
and right now I'm at work) but I will try it again tonight.

At least, I can confirm that it also exists in Netscape 7.01 :
Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0.2) Gecko/20021120

Also, I think this bug is related to bug 161091.

Comment 4

[Boris 'pi' Piwinger]

This here is a dupe. Comment 1 is a dupe of bug 114954. But this is not this
bug, which is a dupe of something else which I cannot find right now. Bug 152825
might be related.

NOT OS-dependend.

pi

Comment 5

[Mike Cowperthwaite]

Bug 161091, mentioned as a potential dupe of this one, had a response a month 
ago that it appeared to have been fixed in 1.4 (rc3 == final); I can confirm 
that and am about to mark that one WorksForMe.

This bug also appears to be have been fixed in 1.4; reporter ([e-mail]), 
if you can confirm, please mark this one WorksForMe as well.

Boris, you may have noticed that bug 152825 was opened by the same reporter as 
this bug.  A recent comment there suggests that bug also is now fixed in 1.4, 
which I can confirm with my testing.  I agree this is probably a dupe of that, 
but at this point we can wait for reporter to WFM them both.

Comment 6

[u32858]

Hello,

It appears to all work for me! resolving!

Thank you for following up this.

JG

Comment 7

[Mike Cowperthwaite]

Verifying WFM.  (Move your votes, folks!)