wrong comment for charset parameter in nsIMsgHeaderParser.idl

RESOLVED WORKSFORME

Status

MailNews Core
Backend
RESOLVED WORKSFORME
16 years ago
9 years ago

People

(Reporter: kaie, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

16 years ago
dmose believes the comment in nsIMsgHeaderParser.idl, saying that default
charset is us-ascii when no charset is specified, is wrong. He believes the
default is UTF8.

If that is true, the comment should get changed.

The implementation seems to ignore the charset parameter at all, but seems to
walk over the string by detecting UTF8 chars.

Updated

16 years ago
QA Contact: gayatri → stephend
Product: MailNews → Core

Updated

9 years ago
Assignee: mscott → nobody
QA Contact: stephend → backend
(Assignee)

Updated

9 years ago
Product: Core → MailNews Core
Charset arguments in nsIMsgHeaderParser.idl are a thing of the past now.
Status: NEW → RESOLVED
Last Resolved: 9 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.