Closed
Bug 1138069
Opened 10 years ago
Closed 6 years ago
seamonkey-2.32.1 mail: image attachment "cannot be displayed because it contains errors"
Categories
(SeaMonkey :: MailNews: Message Display, defect)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: marcoep, Unassigned)
Details
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:35.0) Gecko/20100101 Firefox/35.0 SeaMonkey/2.32.1
Build ID: 20150218163047
Steps to reproduce:
Since some time (4-5 releases?) I can't display anymore, in the main browser window, images attached to an (IMAP) email message.
For info, I have several add-ons installed included NoScript and ADB+ (no $kype ****, though), but the problem persists even in *safe-mode* with all the display permissions (I could find) enabled. No related messages are shown in the error console.
It could be a regression -- I tried to reopen this old Bug 222032 (though this happens on Linux), but have no right for that (?)
1. Open a en email with attached PNG or JPG (didn't try with other form formats)
2. Expand the "Attachments" box
3. [Double] click, or right click -> "Open", on the image file
Actual results:
A browser tab/window opens displaying the error message "Image <imap file address> cannot be displayed because it contains errors". Odd enough, that message is apparently rendered as text, as I can't copy/paste it 8-/
Expected results:
A browser tab/window open displaying the image.
Summary: seamonkey-2.31.2 mail: image attachment "cannot be displayed because it contains errors" → seamonkey-2.32.1 mail: image attachment "cannot be displayed because it contains errors"
![]() |
||
Comment 1•10 years ago
|
||
I'm wondering if this is related to bug 893776.
More info. With SM-2.30 on Arch Linux and same add-on set-up the problem doesn't occur.
Comment 3•6 years ago
|
||
Do you stil lsee this when using a current version?
Flags: needinfo?(marcoep)
Nope! OK with v2.49.9.1_p0 (Funtoo build) :-)
Flags: needinfo?(marcoep)
Status: UNCONFIRMED → RESOLVED
Closed: 6 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•