Closed Bug 272056 Opened 21 years ago Closed 20 years ago

message font changes when mouse moved over "options/character encoding"

Categories

(Thunderbird :: Message Compose Window, defect)

x86
Linux
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED EXPIRED

People

(Reporter: david.newman, Assigned: mscott)

Details

User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20041116 Firefox/1.0 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20041116 Firefox/1.0 A spam email I received had charset="iso-3747-1" in the header, which I think is invalid. When viewing the message, the font of the message body is normal; if I click reply or forward then the font changes to one full of math symbols. The problem is that when I then move the mouse over "Options/Character Encoding" on the message window menubar, the font switches back to normal (i.e. without me actively selecting anything in the menu). Tested with the 0.9 release and the 2004-11-27 nightly build. Reproducible: Always Steps to Reproduce: 1. Receive a message with the line "Content-Type: text/plain; charset=ISO-3747-1;" in the header. 2. Click on Forward, the font should be garbage. 3. Move the mouse over "Options/Character Encoding" on the message window menubar, the font should switch back to normal. This is an email that recreates the problem for me: From - Sat Nov 27 23:41:04 2004 X-Mozilla-Status: 0001 X-Mozilla-Status2: 00000000 Return-path: <...> Envelope-to: <...> Delivery-date: Sat, 27 Nov 2004 23:41:00 +0000 Received: <......> Message-ID: <...> Date: Sat, 27 Nov 2004 23:40:58 +0000 From: <...> User-Agent: Mozilla Thunderbird 0.9 (X11/20041119) X-Accept-Language: en-us, en MIME-Version: 1.0 To: <...> Subject: subject X-Enigmail-Version: 0.89.0.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=ISO-3747-1; format=flowed Content-Transfer-Encoding: 7bit Message body Expected Results: When replying/forwarding a message, the font/character encoding in the message window should not change unless the user changes the font or the character encoding manually. My "Fonts and Languages" settings are Outgoing mail: Western (ISO-8859-1) Incoming mail: Western (ISO-8859-1) Apply default encoding to all messages: Not checked Always use the default encoding in replies: Not checked
Confirmed on Thunderbird 1.0.2. Here's part of a mail (Received header cut out) From - Thu Apr 14 10:52:24 2005 X-Mozilla-Status: 0001 X-Mozilla-Status2: 00000000 Return-path: <email@uppsalahem.se> Envelope-to: mini@localhost Delivery-date: Thu, 14 Apr 2005 06:30:11 +0200 FROM: email@uppsalahem.se TO: mini@nada.kth.se SUBJECT: Hyresobjekt, erbjudande X-MIMETrack: Itemize by SMTP Server on uahemim01/uppsalahem(Release 6.0.3|September 26, 2003) at 2005-04-14 06:13:50, Serialize by Router on uahemim01/uppsalahem(Release 6.0.3|September 26, 2003) at 2005-04-14 06:13:50, Serialize complete at 2005-04-14 06:13:50, Itemize by SMTP Server on uahemns01/uppsalahem(Release 6.5.3FP1|December 15, 2004) at 2005-04-14 06:13:50, Serialize by Router on uahemns01/uppsalahem(Release 6.5.3FP1|December 15, 2004) at 2005-04-14 06:28:57, Serialize complete at 2005-04-14 06:28:57 Date: Thu, 14 Apr 2005 06:13:50 +0200 Message-ID: <OFF9F50571.5FCF9A12-ONC1256FE3.00173D47@uppsalahem.se> X-Greylist: Delayed for 00:15:05 by milter-greylist-1.5.10 (mx3.nada.kth.se [130.237.222.96]); Thu, 14 Apr 2005 06:29:36 +0200 (MEST) X-Scanned-By: MIMEDefang 2.36 MIME-Version: 1.0 Content-Type: text/plain; charset=unknown-8bit Content-Transfer-Encoding: 8bit X-Spam-Checker-Version: SpamAssassin 3.0.1 (2004-10-22) on kmr.nada.kth.se X-Spam-Level: X-Spam-Status: No, score=-2.0 required=5.0 tests=BAYES_00,NO_REAL_NAME, SARE_SUB_COMMA_LEAD autolearn=no version=3.0.1 ERBJUDANDE OM LÄGENHET
Should add that the message content is in latin-1, but header says utf-8
This is an automated message, with ID "auto-resolve01". This bug has had no comments for a long time. Statistically, we have found that bug reports that have not been confirmed by a second user after three months are highly unlikely to be the source of a fix to the code. While your input is very important to us, our resources are limited and so we are asking for your help in focussing our efforts. If you can still reproduce this problem in the latest version of the product (see below for how to obtain a copy) or, for feature requests, if it's not present in the latest version and you still believe we should implement it, please visit the URL of this bug (given at the top of this mail) and add a comment to that effect, giving more reproduction information if you have it. If it is not a problem any longer, you need take no action. If this bug is not changed in any way in the next two weeks, it will be automatically resolved. Thank you for your help in this matter. The latest beta releases can be obtained from: Firefox: http://www.mozilla.org/projects/firefox/ Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html Seamonkey: http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.