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
On 1/18/12 10:00 PM, Elliott Sprehn wrote:
SVG taints the canvas in every browser I've tried
You should try a Firefox aurora (soon to become beta) build, then.
See https://bugzilla.mozilla.org/show_bug.cgi?id=672013
Whether other UAs can fix this bug on their end faster than they can add
On Thu, Jan 19, 2012 at 4:09 PM, Boris Zbarsky bzbar...@mit.edu wrote:
Whether other UAs can fix this bug on their end faster than they can add
various canvas APIs is an interesting discussion, I suppose.
Of course it's vastly better for the Web platform for browsers to fix their
bugs than
On Wed, Jan 18, 2012 at 7:25 PM, Robert O'Callahan rob...@ocallahan.orgwrote:
On Thu, Jan 19, 2012 at 4:09 PM, Boris Zbarsky bzbar...@mit.edu wrote:
Whether other UAs can fix this bug on their end faster than they can add
various canvas APIs is an interesting discussion, I suppose.
Of
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 Thu, Jan 19, 2012 at 4:30 PM, Elliott Sprehn espr...@gmail.com wrote:
Gecko completely punts rendering foreignObject to a canvas
I don't think it does. See
http://robert.ocallahan.org/2011/11/drawing-dom-content-to-canvas.html and
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
