Re: handling fallback content for still images

BTW, my test was flawed. Safari/WebKit handles this content as it  
should and is interoperable with the other XHTML UAs. In other words  
these visual UAs display the image and ignore the contents of the XML  

As others have pointed out, they do not provide the contents of the  
element as fallback for a bad URL.

This forking of fallbacks also accompanies a bigger issues of lossy  
conversion between serializations.

Finally, no tests have been made of any aural and tactile UAs to see  
if they can discover the fallback content.

On Jul 5, 2007, at 4:18 PM, Robert Burns wrote:

> I had another thought about a a long-term solution (and basically  
> this is about long-term solutions) anyway.. Is it possible that, by  
> moving to an xml serialization, this problem will be solved? In  
> other words, can we just do <img src="myimage' >fallback</img>  
> whenever HTML5 content is served as XML. To me this should work (at  
> least as a complement to the other solutions).

Take care,

Received on Thursday, 5 July 2007 22:47:55 UTC