Open
Bug 487128
Opened 17 years ago
Updated 3 years ago
Automatic conversion to plain text adds markup to message
Categories
(Thunderbird :: Message Compose Window, defect)
Thunderbird
Message Compose Window
Tracking
(Not tracked)
NEW
People
(Reporter: mdudziak, Unassigned)
Details
(Whiteboard: [penelope_wants])
The Conversion to plain text when an address matches a plain text domain is a bit broken. For example, this is what is received:
THIS IS NORMAL
*THIS IS BOLD
/THIS IS BOLD ITALICS
_THIS IS BOLD ITALICS UNDERLINE_
/*
I did NOT use any of the characters ‘*_/’ when I composed that
To reproduce:
- Add your domain (or a test domain) to the list of plain text domains (Preferences->Composition->General->Send Options...->Plain Text Domains)
- New message with bold, italics, underline, etc.
- Send message to the plain text domain above
- View received message
- Note there is no bold, italics etc., as expected
- Note there is added markup that is no desired.
| Reporter | ||
Updated•17 years ago
|
Whiteboard: [penelope_wants]
Comment 1•17 years ago
|
||
No, the conversion isn't broken, the display is. You're reporting at least three different libmime bugs, bug 122876 because multiline structs have always been broken, bug 158706 because nesting only works if it doesn't start or end at the same place, and one that escapes me at the moment, about either having libmime remove the */_ rather than wrapping it in a <span class="moz-text-tag"> (which would probably be lossy somewhere, maybe change of format on reply) or having a style rule to make .moz-text-tag display: none.
(Though if penelope_wants to not send structs, moving the dataloss to conversion instead of display, all you have to do is default converter.html2txt.structs to false.)
Updated•3 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•