Closed
Bug 265657
Opened 20 years ago
Closed 20 years ago
Some users compose doesn't autodetect HTML correctly
Categories
(MailNews Core :: Composition, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 187064
People
(Reporter: baffoni, Assigned: sspitzer)
Details
On some users's machines at my company, it refuses to properly autodetect when to send as HTML. In fact, it pointedly ignores the "send as both HTML and Plain" setting and only sends as plain. On other machines, it works correctly. Steps to reproduce: 1) open an email in HTML editor (BTW, wish I had a way to flip between plain/HTML editors while editing), insert a table, go aehad and bold/underline some text. 2) send message with the "send as HTML and Plain" setting in preferences, but don't mess with the message compose's "auto-detect". 3) send message Expected behavior: It should autodetect the markedup content and send as either HTML, or at least follow the preferences setting and send as both. Actual behavior: It sends out as plain text, regardless of preferences setting. Odd workaround: If you manually select "send as both HTML and Plain" from the compose window, it sends out the email properly as both HTML and Plain text. Mozilla 1.7.3 (Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.3) Gecko/20040910). I realize this is probably a pref.js issue, but I'd like a fix that doesn't require resetting up the profile from scratch (I'd have to do that on some 80 users +, and no guarantee it won't come back).
Comment 1•20 years ago
|
||
If the recipient of the email is either listed in the address book as "prefers plain" *or* is unlisted in the address book entirely (bug 257686), the message will be converted to plain text on sending. Bug 246758 requests a prompt before converting to HTML. *** This bug has been marked as a duplicate of 187064 ***
Status: NEW → RESOLVED
Closed: 20 years ago
Resolution: --- → DUPLICATE
Updated•20 years ago
|
Product: MailNews → Core
Updated•16 years ago
|
Product: Core → MailNews Core
You need to log in
before you can comment on or make changes to this bug.
Description
•