User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040113 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040113 The ability to block the fetching and display of images in HTML mail messages is an important safeguard. However, there are times when a message from a trusted source should be displayed as intended. Mozilla should allow a user to toggle the image blocking on or off for the current message easily. Reproducible: Always Steps to Reproduce: 1. 2. 3.

Why not use "View -> Message Body As -> Original HTML" ?

My bad - you actually mean blocked images. Dup of bug 47475 *** This bug has been marked as a duplicate of 47475 ***

there's also bug 57505

I've looked at 47475 and 57505, but neither of these resolves the problem for Mozilla mail. The only right context menu option is "View image", which displays a single image in a separate Navigator window. There are three problems with this: 1) There's no visual indication in the message of where the images are supposed to go, so no cues about where to right-click, 2) The image appears in a separate window, rather than in place, and 3) there's no way to make all the images visible. Thanks.

(In reply to comment #4) > I've looked at 47475 and 57505, but neither of these resolves the problem for > Mozilla mail. The only right context menu option is "View image", which > displays a single image in a separate Navigator window. There are three > 1) There's no visual indication in the message of where the > images are supposed to go, so no cues about where to right-click > 2) The image appears in a separate window, rather than in place, > 3) there's no way to make all the images visible. Item (3) is in fact addressed by bug 57505, which makes (1) moot. Item (2) is not an argument against either bug, it's the problem with the current View Image context menu item. The only possible uniquity to this bug vs. bug 57505 is that you are asking for a "toggle" -- implying the ability to also hide all images once they've already been loaded. I'm not sure that's actually useful, but it's worth considering. Making this dependent of that bug for now, altho I think it's more likely a dupe. Also dropping severity to 'enhancement.'

let's try this one then. *** This bug has been marked as a duplicate of 172184 ***