[rfc-i] Graceful degradation is key, was: Re: draft-hildebrand-html-rfc
Joe Hildebrand (jhildebr)
jhildebr at cisco.com
Tue Jul 17 01:09:44 PDT 2012
On 7/16/12 11:43 PM, ""Martin J. Dürst"" <duerst at it.aoyama.ac.jp> wrote:
>On 2012/07/14 18:34, Iljitsch van Beijnum wrote:
>> Providing bitmap alternatives for SVG and MathML elements is not that
>>much extra work once we figure out a way to automatically display the
>>highest quality version supported.
>It's possible that this doesn't work for *inline* SVG, but in general,
>the <object> element does this.
Ah, but it appears there's more than one way to inline, at least with
Chrome and Firefox:
The relevant part:
<object type="image/svg+xml" data="data:image/svg+xml;base64,...
>Here's an example:
><object type="image/svg+xml" data="image.svg" height="200" width="200">
> <object type="image/png" data="image.png">
> An image of something.
>SVG gets rendered if the browser can render it; if not, PNG gets
>rendered, and if that's also not possible, the text gets rendered.
I really like this approach.
I had been scared to bring <object> into this because of possible security
issues, but I think that might have been unwarranted. Probably the RFC
Editor's tooling will need to check to make sure that only a small number
of media types are accepted, and ensure that they're all embedded like
More information about the rfc-interest