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: Tue, 3 Jul 2007 04:52:34 -0500
Message-Id: <3A9B8759-4C28-42C5-800F-9B2269333FC5@robburns.com>
Cc: public-html@w3.org
To: Sander Tekelenburg <st@isoc.nl>


On Jul 3, 2007, at 4:27 AM, Sander Tekelenburg wrote:

>
> Yeah, those are the big ones. Mainly, how to not have <picture>'s  
> textual
> fallback rendered in pre-HTML5 UAs.
>
> An attempt at finding a possible solution:
> <http://santek.no-ip.org/~st/tests/picturetag/>.

I was trying to set something like this up on the wiki, but I don't  
think it's going to work there.
<http://esw.w3.org/topic/HTML/SimpleObject>

Would you mind trying something like this for fallback:
<picture src="Acid2.png"> <object data="Acid2.png"> <param  
name="src"  value="Acid2.png" >fallback </object> </picture>

Though this is rather complicated in the short-term, it would allow  
us to deprecate (drop/omit/remove) <img> from the spec (leaving it  
only for UA conformance). Then in an HTML5 future we would only use  
<picture src="Acid2.png"> fallback</picture>.

I guess we'd need to see how the above worked in existing UAs and  
then see if any further adjustments are necessary.



Take care,

Rob
Received on Tuesday, 3 July 2007 09:52:43 UTC

This archive was generated by hypermail 2.3.1 : Monday, 29 September 2014 09:38:46 UTC