If you create an MHTML message with embedded objects (images, etc..), send the message and the send operation fails, the embedded objects are trashed. This is because we whack the DOM links with the cid:'s of these objects for creation of the MHTML message. The right thing to do would be to keep track of embedded objects and their associated DOM nodes and when a send operation fails, restore the orginal links.
Summary: Embedded MHTML objects trashed when send operation fails → [FIXED] Embedded MHTML objects trashed when send operation fails
This is fixed in my tree. - rhp
Status: ASSIGNED → RESOLVED
Last Resolved: 19 years ago
Resolution: --- → FIXED
Summary: [FIXED] Embedded MHTML objects trashed when send operation fails → Embedded MHTML objects trashed when send operation fails
All better now. - rhp
Rich - do you mean when the send operation fails and then the app brings you back to the compose window? The bug was the embedded objects would be corrupted if you tried to resend the msg again? Just trying to understand so we can verify this.
An easy test would be to send a message with an embedded image. If you did this, and if failed, you would have a broken image link when you got the compose window back. - rhp
Build ID: 2000-06-09-08 NT Verified: RESOLVED FIXED
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.