202654 - viewing message body as plain text doesn't always use monospace font size from prefs

Status: RESOLVED EXPIRED

(SeaMonkey :: MailNews: Message Display, defect)

Description

[Felix Miata]

Tested currently in Linux 2003041808 and OS/2 2003032009 trunks, but older than
I can remember.

To reproduce:
1-display a message with typical iso-8859-1 character encoding
2-set 'view->message body as->plain text'
3-display a message not using iso-8859-1 character encoding (e.g. iso-8859-2,
iso-8859-9, or koi8-r)

Actual results:
1-iso-8859-1 messages display using monospace font size set in prefs
2-other charset encoded messages display using a smaller size than the monospace
font size set in prefs. NAICT, the size is 13px, which is the default size in a
fresh/unmodified profile.

Expected results:
1-all messages display using monospace font size set in prefs

Notes:
Messages not using iso-8859-1 aren't necessarily easy to find. I'm attaching
screenshots of messages using other encodings mentioned above, as well as the
baseline 16px lucida console for comparison. The screenshots all include
sufficient info to load each live off the news.mozilla.org news server.

Comment 1

[Felix Miata]

Attachment: iso-8859-1 encoded message screenshot (normal)

Comment 2

[Felix Miata]

Attachment: iso-8859-2 encoded message screenshot

Comment 3

[Felix Miata]

Attachment: koi8-r encoded message screenshot

Comment 4

[Felix Miata]

Attachment: iso-8859-9 encoded message screenshot

Comment 5

[Felix Miata]

As the screenshots show, the text size used to display each message is also the
size used to 'view->message source'.

Comment 6

[R.K.Aa.]

Reporter: Are you still seeing this bug?

Comment 7

[Dave Kimberley]

I also see this bug on Mozilla 1.8a3, Windows XP Service Pack 2.

Comment 8

[Dave Kimberley]

On further investigation seems to be a duplicate of bug 227850

Comment 9

[Felix Miata]

It took me a long time to find any posts that are not either 8859-1 or us-ascii
(or no charset header at all). In current trunk on Linux, when I found the
first, charset=EUC-KR, that did it, I quit looking for more. So yes, this bug
still exists.

Dave, we don't dupe newer branch build bugs to older trunk build bugs. 227850
should probably be duped to this.

Comment 10

[Robert Kaiser]

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 11

[Robert Kaiser]

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago.

Because of this, we're resolving the bug as EXPIRED.

If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component.

Query tag for this change: EXPIRED-20100420

Comment 12

[Felix Miata]

Probably this still exists, but I have no idea if or when I'll find the considerable time this will probably require to purposely confirm.