W3C home > Mailing lists > Public > public-html@w3.org > July 2007

Re: handling fallback content for still images

From: scott lewis <sfl@scotfl.ca>
Date: Sun, 8 Jul 2007 20:52:48 -0600
Message-Id: <EEDEDFF9-88C0-4D1C-A832-E88D67BDF6AC@scotfl.ca>
Cc: HTML Working Group <public-html@w3.org>
To: Jon Barnett <jonbarnett@gmail.com>

On 8 Jul 2007, at 1954, Jon Barnett wrote:

> Scott Lewis wrote:
> Some UAs do even today. In quick testing, serving an XHTML1 Strict
> document[1] with an application/xhtml+xml doctype resulted in:
>  - Safari 3 beta inserting the <tbody>
>  - Opera 9.21 not inserting the <tbody>
>  - Firefox and refusing to render the document
>  - IE 7.0.5730.11 rendering the document as if the <tbody> were
> inserted (I didn't check the DOM for it's presence)
> Did you see my test documents and my messages above? [1]  When  
> parsed as HTML and rendered in standards-compliance mode, ALL  
> browsers insert the <tbody> element.  When parsed as XML in  
> standards compliance mode, no browsers insert the <tbody> element  
> (this is expected), except IE which can't properly handle XHTML.
> This is not "wildly inconsistent".
> http://lists.w3.org/Archives/Public/public-html/2007Jul/0472.html

I was looking at XHTML 1.0  Strict served as application/xhtml+xml.  
Which is what Thomas was specifically talking about and your tests  
didn't cover. I hadn't intended to be dismissive or disparaging of  
your tests, I apologize if it came across that way.

FWIW, my copy of Safari 3 beta inserts the <tbody> into both of your  
test pages.

Received on Monday, 9 July 2007 02:52:54 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 29 October 2015 10:15:24 UTC