Inline images or embedded local files silently stripped without trace when force-sending HTML message in plaintext mode (Options > Format > Plain Text only: img lost; need warning and/or conversion into attachments)
Categories
(MailNews Core :: Composition, defect)
Tracking
(Not tracked)
People
(Reporter: bugzilla, Unassigned)
References
(Blocks 3 open bugs, )
Details
(Keywords: dataloss, helpwanted)
| Reporter | ||
Comment 1•24 years ago
|
||
Comment 3•23 years ago
|
||
Comment 4•23 years ago
|
||
Comment 5•22 years ago
|
||
Comment 6•22 years ago
|
||
Comment 7•22 years ago
|
||
Comment 8•22 years ago
|
||
Comment 9•22 years ago
|
||
Comment 10•22 years ago
|
||
Comment 11•22 years ago
|
||
Comment 12•22 years ago
|
||
Comment 13•22 years ago
|
||
Updated•21 years ago
|
Comment 14•21 years ago
|
||
Comment 15•21 years ago
|
||
Comment 16•21 years ago
|
||
Comment 17•20 years ago
|
||
Comment 18•19 years ago
|
||
Comment 19•19 years ago
|
||
Updated•19 years ago
|
| Assignee | ||
Updated•18 years ago
|
Comment 23•14 years ago
|
||
Updated•14 years ago
|
Updated•13 years ago
|
Comment 25•11 years ago
|
||
Comment 26•10 years ago
|
||
Comment 27•8 years ago
|
||
Comment 28•6 years ago
|
||
Thomas, would that have been mitigated in bug 1222176? I came here from bug 1602445 comment #4.
Comment 29•6 years ago
•
|
||
(In reply to Jorg K (GMT+1) (PTO to 5th Jan 2020, sporadically reading bugmail) from comment #28)
Thomas, would that have been mitigated in bug 1222176? I came here from bug 1602445 comment #4.
Probably yes, depending on scenarios / to some extent, but not completely. Bug 1222176 attempts to rectify/improve recipient-centric auto-detect format determination, so for mixed recipients preferences, and depending on settings, it may err in favor of HTML more often with default settings. Bug 1222176 also makes user's conflict resolution apply to allPlain recipient scope, so for conflict resolutions "send HTML" or "send BOTH", again cases which currently fail would be saved. However, even after bug 1222176, if you set your conflict resolution to "send PLAIN", silent dataloss would still occur after sending for any messages having at least one prefers-plain recpient. Same when you force your message directly to be sent in plain (options > delivery format > plain), this dataloss would always occur. That type of dataloss should NEVER occur, so this is a bug in its own right. Note that bug 1222176, iirc, was scaled down for compromise and acceptability to only have one combined preference for "allPlain" and "somePlain", but in theory, these recipient scopes may require different conflict resolutions. The whole behaviour would be far more controllable, predictable, and less buggy, less false promises with Bug 1222176; but ultimately, I'm still suspecting that the only cure for recipient-centric auto-detect, especially in the current shape of "trash message AFTER sending", is to rip it out and replace with an identity-centric solution. I could do that if I get paid.
Also note that the whole story involves those other bugs where we don't enforce, before sending, a WYSIWYG composition experience for the message format that will actually get sent, i.e. we don't do live conversions, and we don't have a switch for that (bugs on record). I think even the "real" plaintext editor still allows pasting images and HTML, worse when you compose HTML and just force plaintext for sending (read: after sending) - no immediate conversions, warnings, etc. It's a massive mess, so Bug 1222176 alone would NOT dry out the entire cesspool, but nevertheless improve things a lot.
Sorry, no short answers here - it's in the complexity of the matter.
| Comment hidden (advocacy) |
Comment 32•4 months ago
|
||
get automatically converted to plain text because the recipient is listed to accept only plain text.
Is this still a thing?
Comment 33•4 months ago
|
||
The recipient-based logic was removed in bug 1727493, so it's no longer a thing. However, the behaviour is still there:
Inline images or embedded local files silently stripped without trace when force-sending HTML message in plaintext mode.
"force-sending" these days means that the user asked for "plaintext only", either generally in the compose settings of via "Options > Sending Format".
Comment 34•4 months ago
|
||
(In reply to Francesco from comment #33)
The recipient-based logic was removed in bug 1727493, so it's no longer a thing. However, the behaviour is still there:
Inline images or embedded local files silently stripped without trace when force-sending HTML message in plaintext mode.
"force-sending" these days means that the user asked for "plaintext only", either generally in the compose settings of via "Options > Sending Format".
Sending html as forced plaintext can yield other stupid results as well that are worth investigating.
Description
•