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

Re: handling fallback content for still images

From: Robert Burns <rob@robburns.com>
Date: Thu, 5 Jul 2007 04:49:44 -0500
Message-Id: <6BC08954-9C58-4F32-96D7-EEF94E0B8B72@robburns.com>
Cc: HTML WG <public-html@w3.org>
To: Henri Sivonen <hsivonen@iki.fi>

On Jul 5, 2007, at 4:44 AM, Henri Sivonen wrote:

> On Jul 5, 2007, at 12:29, Robert Burns wrote:
>> I added the <img>fallback</img> for xml serialization solution to  
>> the Longdescription page. If anyone can think of any other pros  
>> and cons, please add them.
>> <http://esw.w3.org/topic/HTML/LongdescRetention#preview>
> Pros list "Already works in some UAs".
> Which existing UAs use the content of <img> as fallback in  
> application/xhtml+xml? (That is, which existing application/xhtml 
> +xml UAs present the content of the <img> element to the user in  
> the situations and only in the situations where they'd present the  
> value of the alt attribute?) What happens in those UAs when both  
> element content and the alt attribute is present?

Should I say "doesn't break some existing UAs". In other words, with  
XML those UAs do not inappropriately present the fallback content.  
With text/html we had amore severe problem where this would break  
with all visual UAs. So how ever best to word that pro, please go  
ahead and and away.. I haven't tested any of the aural UAs yet. I'd  
be happy to hear what you find out if you've tested anything else.

Take care,
Received on Thursday, 5 July 2007 09:50:01 UTC

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