Confirm
2,236
edits
Changes
→Attachments & MIME bugs: added 307023 and more details for 65794
== Attachments & MIME bugs ==
[https://bugzilla.mozilla.org/show_bug.cgi?id=65794 Bug 65794]: The default setting for an attachment's Content-Disposition is 'inline' (and there is no UI to change it). "very old, very annoying, gets lots of dupes, and is easily fixable. See also [http://forums.mozillazine.org/viewtopic.php?p=536030 this mz thread]."Comment to this bug are about which default is appropriate, to which attachments the preference should be applied (not for all MIME types an 'inline' disposition makes sense), and how a user could specify the disposition type while attaching.
[https://bugzilla.mozilla.org/show_bug.cgi?id=147461 Bug 147461] and [https://bugzilla.mozilla.org/show_bug.cgi?id=229075 bug 229075]: The actual handling of Content-Disposition is inconsistent; types that Mozilla knows how to render (image/jpeg, text/plain) will be shown inline even with Content-Disposition set to 'attachment', and other attachments with Content-Disposition set to 'inline' are not shown inline. This latter problem can even suppress display of the message body itself ([https://bugzilla.mozilla.org/show_bug.cgi?id=182627 bug 182627]).
[https://bugzilla.mozilla.org/show_bug.cgi?id=244618 Bug 244618]: TB does not allow the user to define and edit MIME types and their associations to file extensions and programs, following the model implemented by Firefox. While Firefox can get away with this because it's only dealing with incoming files, TB can <em>send</em> files as attachments, and it would be nice if the users could configure the program to provide the correct MIME type when sending it out. This bug is a request-for-enhancement, but it's an enhancement that's sorely needed.
[https://bugzilla.mozilla.org/show_bug.cgi?id=307023 Bug 307023]: Attributes of HTML messages received in quoted-printable or other complex Content Transfer Encodings may get corrupted when the message is re-edited (e.g., forwarded, potentially replied to, or opening own messages after saving them as draft). This causes substantial problems, such as loss of images embedded in the HTML, which cannot be explained by the average user.
=== RFC822 Attachments and .EML files ===
