• To: Eric van der Vlist <vdv@d...>
• Subject: Re: SVG interoperability
• From: Mitch Amiano <mitch.amiano@a...>
• Date: Mon, 19 Jun 2006 09:44:11 -0400
• Cc: "xml-dev@l..." <xml-dev@l...>, robin.berjon@e...
• In-reply-to: <5076F73E-C0A4-47AC-BAF5-7E062E6474C5@e...>
• References: <1150365359.19638.53.camel@l...> <F453CCBA-48F3-4801-8F60-C1CAB43830D1@e...> <1150703677.4501.42.camel@l...> <5076F73E-C0A4-47AC-BAF5-7E062E6474C5@e...>
• User-agent: Thunderbird 1.5.0.4 (Windows/20060516)

Robin Berjon wrote:
> On Jun 19, 2006, at 09:54, Eric van der Vlist wrote:
>
>> When your users upgrade to Firefox 1.5, they will very probably not be
>> able to render your SVG pages any longer and, what's worse, these
>> failures are silent, there is no warning of any kind that mention that
>> the browser has found features that it can't render and no way for a web
>> app to detect that and suggest to install a plugin and disable native
>> SVG support.
>
> I haven't investigated but I think there may be a way of telling 
> Firefox to use a plugin no matter what.
>

There is. See http://www.mozilla.org/projects/svg/faq.html#svg-plugin

• Follow-Ups:
  • Re: SVG interoperability
    • From: Robin Berjon <robin.berjon@e...>

• References:
  • SVG interoperability
    • From: Eric van der Vlist <vdv@d...>
  • Re: SVG interoperability
    • From: Robin Berjon <robin.berjon@e...>
  • Re: SVG interoperability
    • From: Eric van der Vlist <vdv@d...>
  • Re: SVG interoperability
    • From: Robin Berjon <robin.berjon@e...>

• Prev by Date: Re: XML 2006 proposals due today
• Next by Date: Re: SVG interoperability
• Previous by thread: Re: SVG interoperability
• Next by thread: Re: SVG interoperability
• Index(es):
  • Date
  • Thread