- From: fantasai <fantasai.lists@inkedblade.net>
- Date: Wed, 14 Mar 2012 12:46:30 -0700
- To: Philippe Le Hegaret <plh@w3.org>
- CC: "Tab Atkins Jr." <jackalmage@gmail.com>, Cameron McCormack <cam@mcc.id.au>, spec-prod <spec-prod@w3.org>
On 03/14/2012 08:29 AM, Philippe Le Hegaret wrote: > On Wed, 2012-03-14 at 07:51 -0700, Tab Atkins Jr. wrote: >> Here's something even simpler: >> >> <!doctype html> >> <figure> >> <svg> >> <defs> >> <foreignObject> >> <img src="fallback.png" /> >> </foreignObject> >> </defs> >> ...real image here >> </svg> >> <figcaption>I'm an image!</figcaption> >> </figure> >> >> In UAs that support SVG, the<img> will never be rendered. In UAs >> that don't, you'll just get an<img> wrapped up in a bunch of unknown >> inline elements. > > > but if you have a text element in your SVG, that text node will be > visible if the agent doesn't understand inline SVG, leading to messy > text. Sorry, I seem to have missed some context here... what is the problem with using <object> and an external image reference? ~fantasai
Received on Wednesday, 14 March 2012 19:47:11 UTC