306198 - Inline PNG image is not displayed

Status: VERIFIED INVALID

(SeaMonkey :: General, defect)

Description

[boogs]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.11) Gecko/20050728
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.11) Gecko/20050728

The above URL is the Wikipedia image description page for a PNG image; the page
contains the associated image
(http://upload.wikimedia.org/wikipedia/en/a/ad/Wikibooks-logo-PROTECTED.png) as
an inline image, but the image is not displayed by Mozilla.

The image is displayed fine when loaded directly, so it's not the image itself
that is the problem; the containing page validates as XHTML 1.0/Transitional
using the w3c's online validator, so a problem caused by bad HTML can be ruled
out as well.

It's also noteworthy that Opera 8 displays the page correctly, including the
image, which further suggests that the problem lies with Mozilla rather than
with the page.

Please get back to me if you need any further information. Thanks!

Reproducible: Always

Steps to Reproduce:

Comment 1

[Christian :Biesinger (don't email me, ping me on IRC)]

What are your settings in Preferences/Privacy&Security/Images? Especially, is
"Accept images that come from the originating server only" checked?

Comment 2

[boogs]

No - it's set to "Accept all images" (and "Animated images should loop as many
times as the image specifies", but I think that's not really relevant). The list
of sites that can/can't load images is empty, too.

FWIW, this is the only Wikipedia image description page I have encountered so
far that exhibits this problem - all the other ones work fine, both for PNGs and
for non-PNGs.

Comment 3

[Christian :Biesinger (don't email me, ping me on IRC)]

do you have adblock or another advertisement-filter installed? and is it
configured to block URLs containing /ad/?

Comment 4

[Stefan [:stefanh]]

Image displays fine here with the 1.7.11 release and in a recent trunk build (mac).

Comment 5

[boogs]

Darn! Yes, you were right, it was due to AdBlock - or, rather, due to my own
stupidity (filtering */ad/* probably is a bit *too* excessive, it seems). Sorry
- I should've realised this earlier, but I was thrown off track when a friend of
mine (who probably also uses AdBlock) confirmed this behaviour...

Sorry. :)