Not Asking if variable width text is body, paragraph, or preformatted.

VERIFIED WORKSFORME

Status

MailNews Core
Composition
VERIFIED WORKSFORME
17 years ago
10 years ago

People

(Reporter: hirata masakazu, Assigned: Jean-Francois Ducarroz)

Tracking

Trunk
PowerPC
Mac System 9.x

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Reporter)

Description

17 years ago
2001021608MTrunk.
This is related to error handling problem in 57083.
In preference, Send Format is set to Ask me what to do.
In Mail compose window, Format is Autodetect.
In Mail/News Account Settings, Compose as HTML is checked ON.
Compose a message that contains characters not supported as in bug 57083.
Send and get the warning.
Since it is not your fault that those characters can not be handled by Mozilla,
you just OK to proceed and message is sent.
The result: you never get a chance to be asked what to do about the format.
(Reporter)

Comment 1

17 years ago
Created attachment 25521 [details]
characters in SJIS used to test the Mail composer

Comment 2

17 years ago
I did not see the problem using win32 6.01. It may be a Macintosh specific.
(Reporter)

Comment 3

17 years ago
I have realized this has nothing to do with character code warnings.
Mozilla does not care if the text is variable width. It simply decides to send
in plain text if there is no other HTML element.
Updating summary and component.
Component: Internationalization → Composition
Summary: Not Asking when character code warning is evoked. → Not Asking if variable width text is body, paragraph, or preformatted.

Updated

17 years ago
Assignee: nhotta → ducarroz

Comment 4

17 years ago
Reassign to ducarroz.
(Reporter)

Comment 5

17 years ago
Looks like it is fixed in 022304 build for MacOS.
Resolving as WFM
Status: NEW → RESOLVED
Last Resolved: 17 years ago
Resolution: --- → WORKSFORME

Comment 6

17 years ago
Checked 04/02 Mac trunk build. Marked it as verified.
Status: RESOLVED → VERIFIED
Product: MailNews → Core
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.