User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030617 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030617 If an mng animated image is included in an html email, it is not displayed when the email is opened by the recipient. It is, however, available as an attachment. The email displays an empty box in the location where the mng image should appear. The mng image is displayed correctly in the compose window. Reproducible: Always Steps to Reproduce: 1.Open mail compose window. 2.Write email and insert an mng animated image. 3.Send email. 4.Receive and open email. Actual Results: The received email displays an empty box at the place where the mng image was inserted. Expected Results: The mng image should be displayed at the location where it was inserted into the message.
Mng-support was recently removed from Mozilla (see bug 195280). That's why you can't display it (in a webpage or in mail), although you can always download the attachment and view it in another application ofcourse. But I'm wondering why you can see it in the compose-window ?
Oh I see. MNG-support was removed from the trunk, not the 1.4 branch. So you want to report that you can see the image in a composer-window, but not in an email ? Will this be INVALID ?
Yes - as I understand it, 1.4 and derivatives will have full mng support. To clarify - When you compose an html email with Mozilla mail and insert an mng image, it displays correctly in the composer window. When you send this email, and a recipient opens it, the mail reader window displays an empty box where the mng image should be, with just the broken link icon in it. The mng image is, however, transmitted in the email and can be opened by means of the attachment pane. I've attached a mng image should you want to try it... Regards, Pete.
extension for windows only, mozilla and firebird/trunk http://extensionroom.mozdev.org/more-info.php/mngsupport
Better yet, attach screenshots showing how the two states are different. That may be more helpful. Since, of course, we can't open MNG images ourselves. ;)
Created attachment 126280 [details] Compose Window This image shows the compose window with the ming animation correctly displayed. Even the preview window on file/select showed the animation running!
Created attachment 126281 [details] Receive window The receive window with the ming animation displayed as a broken link, yet available in the attachment pane. (Right clicking on catrunbar.mng and selecting open displays the animation).
The 1.4 branch have been replaced by the 1.7 branch as a platform for others to build on. Since 1.7 does not include MNG support should this bug not be marked invalid ? We can always take up this issue again when MNG is reintroduced into the Mozilla products.
This is an automated message, with ID "auto-resolve01". This bug has had no comments for a long time. Statistically, we have found that bug reports that have not been confirmed by a second user after three months are highly unlikely to be the source of a fix to the code. While your input is very important to us, our resources are limited and so we are asking for your help in focussing our efforts. If you can still reproduce this problem in the latest version of the product (see below for how to obtain a copy) or, for feature requests, if it's not present in the latest version and you still believe we should implement it, please visit the URL of this bug (given at the top of this mail) and add a comment to that effect, giving more reproduction information if you have it. If it is not a problem any longer, you need take no action. If this bug is not changed in any way in the next two weeks, it will be automatically resolved. Thank you for your help in this matter. The latest beta releases can be obtained from: Firefox: http://www.mozilla.org/projects/firefox/ Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html Seamonkey: http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 13 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.