Closed Bug 1326077 Opened 8 years ago Closed 8 years ago

2.46's quoting issues fails to wordwrap correctly in plain text format when replying.

Categories

(SeaMonkey :: MailNews: Composition, defect)

SeaMonkey 2.46 Branch
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 1288911

People

(Reporter: ant, Unassigned)

Details

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:49.0) Gecko/20100101 Firefox/49.0 SeaMonkey/2.46 Build ID: 20161213183751 Steps to reproduce: 1. Reply to a long e-mail or newsgroup post in plain text. 2. Look at its quoted parts. Actual results: Quoting is all messed up due to wordwrapping not working correctly. https://i.imgbox.com/V8mQVnH2.gif for a screen shot/capture when I was replying to "2.46 data manager not working" newsgroup thread. HTML formats seem OK though. Others and I reproduced this issue in my mozilla.support.seamonkey newsgroup's "V2.46's quoting issues with wordwrapping in plain text format?" thread. Expected results: Quoted parts should look good like in v2.40 and earlier.
Also, manual ctrl+r hotkeys to force a wordwrap seems to fix the issue but that doesn't work well with specific formatting like lists.
Probably DUP of "Bug 1288911 - Quote in Reply with unwanted line wraps (broken quote lines), quote wraps to overall body if mailnews.wraplength > 0" @Ant: Do you agree with DUP of do you see differences between this one and Bug 1288911?
Flags: needinfo?(ant)
Rainer, they do look identical to me. I even tried its draft suggestion and that worked well as a temporary workaround. :D
So DUP of Bug 1288911 for now. @Ant: Please feel free to reopen this Bug if you find out that the fix for the other bug does not solve your problem or if you see other well founded indication that you fond an independent bug
Status: UNCONFIRMED → RESOLVED
Closed: 8 years ago
Resolution: --- → DUPLICATE
Is this fixed in SM v2.46? I still see some of these, but not terrible.
Flags: needinfo?(ant)
FYI. I still see this problem like in my newsgroups' replies.
You need to log in before you can comment on or make changes to this bug.