Bug 11296 – SVG plug-in is used instead of built-in SVG support

• Status: RESOLVED
• Resolution: INVALID
• Component: SVG

If you have the Adobe SVG plugin installed, TOT will use it to render SVG instead of using built-in SVG support. This didn't use to be the case, but I don't know exactly when it changed, since the SVG plugin was unavailable between ~r15924 and r16450 due to bug 10661.

[Alexey Proskuryakov]

I would say this is a good thing - a user who has Adobe SVG Viewer installed probably wants to access "real life" SVGs, and many of those only work with Adobe viewer.

(In reply to comment #1)
> I would say this is a good thing - a user who has Adobe SVG Viewer installed
> probably wants to access "real life" SVGs, and many of those only work with
> Adobe viewer.
> 

I respectfully disagree :-) It is ultimately a "marketing decision" how to handle this in WebKit releases, but in nightly builds there is no reasonable expectation that the plugin be used.

AFAUJ, "a user who has Adobe SVG Viewer installed" is typically just "someone who installed an Adobe application at some point" or "someone who uses SVG with shipping Safari".

[Alexey Proskuryakov]

On the other hand, it is probably a good thing to keep nightly builds as close to the future release as possible, so that there are fewer surprises lurking ahead.

Will "someone who uses SVG with shipping Safari" will have any reason (or will even be able) to switch to the built-in implementation when it ships?

[Alexey Proskuryakov]

This was recently discussed on webkit-dev, and the consensus seems to be that the current behavior is correct.

http://lists.macosforge.org/pipermail/webkit-dev/2006-November/001425.html