Open Bug 130087 Opened 23 years ago Updated 2 years ago

Broken/blocked image, context menu, view image or copy image/location fails.

Categories

(MailNews Core :: MIME, defect)

defect

Tracking

(Not tracked)

People

(Reporter: selmer, Unassigned)

References

Details

3/4 09 099 branch build

I have an email with a broken image in it.  (The image is a plain file name and
there is no base tag in the html.)  Right click view does nothing, at the least
it should give an error dialog.  Right click copy image location does not copy
anything, perhaps that's the best we should try for.

I expected a browser window to open to a broken image with the URL that was
resolved in the URL bar for me to manipulate.
does this also happen for webpages with broken images?
Bienvenu, might this be a regression from that other image-contextmenu bug?
I can't really tell from the bug report. I doubt it - this is the very specific
case of the broken image. My change was only code that gets executed when you
pick "save as" from the right click context menu. 
and since this is on the .9.9 branch, and my fix is trunk-only, it seems highly
unlikely that my change could be responsible.
On a web page with a broken image, the context menu tries to go to the image and
returns a "not found" page.  The copy image location menu does copy the location
and I can then paste it into the URL bar and again see the "not found" page.  

In an email with a non-broken image, everything works as expected.
Changing the web page to have a bogus <base> tag, the menu still works exactly
as expected (although I got a different error page from foo.com :-)
"Copy image location" may be a bug of its own; it also fails on normal webpages,
see bug 163897

"View image" still works on webpages, so maybe the bug should focus on that only.
An easy way to check this bug is to view an HTML message with remote image 
references using View|Body As|Simple, which shows all remote images as broken.

Actually, let me equivocate about that.  In 1.6, the remote images are shown 
with the broken icon, but looking at 1.7a-0301, they are shown with a little 
red-dot icon.  Same symptom as this bug, tho -- you can right click and be 
presented with the the View Image and Copy Image Location items, but neither 
item does anything.  (No JavaScript errors thrown, tho.)
Depends on: 196380
I can confirm on Thunderbird, Aviary branch, 20040811.

Context menu of blocked/broken image shows "Copy Image Location", but "Copy
Image Location" doesn't seem to work.
Flags: blocking-aviary1.0?
not a 1.0 stopper.
Flags: blocking-aviary1.0? → blocking-aviary1.0-
Product: Browser → Seamonkey
Assignee: sspitzer → mail
Assignee: mail → nobody
QA Contact: esther → message-display
Reconfirming for Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.3a1pre) Gecko/20100125 SeaMonkey/2.1a1pre, Copy Image fails on blocked/broken images in messages (tested on remote images in a message without unblocking them).

In contrast to prior comments, "View Image" on a valid but blocked image works for me on SM trunk builds, whereas "Copy Image" doesn't put anything onto the clipboard. I see 'Error: An error occurred executing the cmd_copyImage command: [Exception... "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIController.doCommand]" nsresult: "0x80004005 (NS_ERROR_FAILURE)" location: "JS frame :: chrome://global/content/globalOverlay.js :: goDoCommand :: line 96" data: no] Source File: chrome://global/content/globalOverlay.js
Line: 100' in the error console.

Per comment #9 and bug 541858, also Thunderbird is affected (tested today's 3.2a1pre nightly build), thus moving this to MailNews Core category.
Status: UNCONFIRMED → NEW
Component: MailNews: Message Display → MIME
Ever confirmed: true
OS: Windows NT → All
Product: SeaMonkey → MailNews Core
QA Contact: message-display → mime
Hardware: x86 → All
Summary: Broken image, context menu, view image or copy image location fails. → Broken/blocked image, context menu, view image or copy image/location fails.
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.