142587 - JPEG image loaded by OBJECT tag in XHTML1.0-Strict page does not appear

Status: RESOLVED INVALID

(Core :: Layout, defect)

Description

[Jon Bailey]

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.0rc1)
Gecko/20020417
BuildID:    2002041711


This particular page http://www.jb.org/indexold.html rendered fine under earlier
Mozilla releases under Windows, and under Netscape 6.  It does not have the
license plate GIF image (look at the source) under Mozilla 2002041711-windows...
reported working under Linux.

Reproducible: Didn't try
Steps to Reproduce:
1. View the page.  License plate GIF image is missing.

Comment 1

[Jon Bailey]

Whoop, my typo, the image is a JPEG not a GIF.

(The page was put together as a minimal test of XHTML-1.0-Strict , containing
gif, png, and jpg images, using inline CSS).

Comment 2

[Boris Zbarsky [:bzbarsky]]

I'm sorry, but this bug is invalid.  The page is served as text/html, which
means that we parse it per the HTML parsing rules instead of the XML parsing
rules (we did not use to, which was a bug).   By the way, any non-XML-capable
useragent, which is what XTHML served as text/html is aimed at, would parse it
by the same rules.  Per the HTML parsing rules, we have:

  <p style="text-align: center">
   <object data="lumdance.gif" type="image/gif"
           title="o/~ Anmari sowa-sowa shinaide ... o/~"
           height="202" width="97" />
   <br />
   <object data="jb.jpg" type="image/jpeg" title="jb.org license plate"
           height="149" width="296" />
   <br />
  </p>

The first <object> tag is never closed, since the trailing "/" is not meaningful
in HTML (or rather it is, but does not mean the same thing as it does in XML). 
so the two <br> tags and the second <object> are never shown, since they are
content _inside_ an <object> tag and the <object> is being shown.

If you serve the page with an XML type, we will parse it as XML and show it as
you want it shown.

The point is, the " />" thing in XHTML should only be used on tags that have no
end tag in HTML; it should not be used to indicate that a tag that has to have
an end tag per the HTML DTD should suddenly be treated as an empty tag -- no
HTML parser should respect that.  What you have is a valid XML document but not
a valid HTML document, and you are serving it as text/html....

I have sent mail to [e-mail]
(http://lists.w3.org/Archives/Public/www-validator/2002May/0026.html is the
mail) raising the issue of whether the validator should validate a page in these
circumstances.

Comment 3

[Laura Krietemeyer]

Changing QA Contact