The same origin issues with <img src="doc.svg" /> have a mixed history.
I agree that bit-level rendering in Canvas is impractical for most uses.
I've done a bit of work on authoring tools; I would like to see the same
origin issues with basic SVG references fixed in the near future.
-Charles
On 1/18/12 7:00 PM, Elliott Sprehn wrote:
SVG taints the canvas in every browser I've tried which precludes many
uses of canvas that require toDataURL() to work.
I don't think SVG is a reasonable solution to the lacking features in
the canvas API. Having to decide between bit level access and dotted
lines is not reasonable.
On Sat, Jan 14, 2012 at 12:35 PM, Charles Pritchard <ch...@jumis.com
<mailto:ch...@jumis.com>> wrote:
There have been quite a few threads and requests for extensions to
the Canvas 2d API.
I've been working on some extensions to help Canvas authors meet
WCAG2 conformance, over at public-canvas-api.
I want to point out to all of you, that many of the features you'd
like to see in Canvas can be accomplished via drawImage and SVG.
SVG support in the image element is working in many browsers.
There are many methods available in SVG that are not available in
Canvas. Use SVG images as a means to enable them in your Canvas
interface.
It's not a perfect solution, but for some things, like dotted
lines, it can work out.
