Closed
Bug 275875
Opened 20 years ago
Closed 20 years ago
corrupted display of message body text
Categories
(Thunderbird :: Mail Window Front End, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: rngadam, Assigned: mscott)
Details
Attachments
(1 file)
|
289.30 KB,
image/jpeg
|
Details |
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0 After a migration from Mozilla Mail 1.7.3 to Mozilla Thunderbird 1.0, I've started noticing corruption in the text body of messages, both from NNTP newsgroups and in my mail accounts. Since I migrated, I've just added a few newsgroups and played with the layout. I cannot pinpoint exactly what could have caused this problem. See the screenshot attachment I'll be adding. The message shown in the screenshot should appear like this: http://article.gmane.org/gmane.linux.file-systems/3987 Reproducible: Always Steps to Reproduce: 1. Upgrade from Mozilla Mail 1.7.3 to Thunderbird 2. Read emails and newsgroup posting 3. Actual Results: Message body display corruption Expected Results: No display corruption
| Reporter | ||
Comment 1•20 years ago
|
||
| Reporter | ||
Comment 2•20 years ago
|
||
(sorry about that big image BTW, it is the first time I take a screenshot of my
dual display and didn't notice the right part until it was too late).
I just did a test by creating another profile and the messages display ok in
this other profile.
So I went thru both prefs.js and found this difference:
user_pref("font.name.monospace.x-western", "CSD10");
Upon removing this, the message displays correctly! So I guess it is a
left-over config that shouldn't have been imported to Thunderbird...
I've documented it here:
http://kb.mozillazine.org/index.phtml?title=Thunderbird_:_Issues_:_Corrupted_message_body_displayStatus: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•