W3C home > Mailing lists > Public > public-webapps@w3.org > April to June 2012

Re: exposing CANVAS or something like it to Web Workers

From: Charles Pritchard <chuck@jumis.com>
Date: Mon, 14 May 2012 18:15:51 -0700
Message-ID: <4FB1AE47.5090307@jumis.com>
To: Boris Zbarsky <bzbarsky@MIT.EDU>
CC: "public-webapps@w3.org" <public-webapps@w3.org>
On 5/14/2012 6:08 PM, Boris Zbarsky wrote:
> On 5/14/12 8:58 PM, Charles Pritchard wrote:
>> I agree... Can we get this off the main thread?
>
> "Maybe".
>
> It would be pretty nontrivial in Gecko; last I looked it would be 
> pretty painful in WebKit too.  Can't speak for other UAs.

Can it be pumped through what's essentially an iframe on a null origin?

I don't know enough about browser internals to help on this one.
Yes, loading an SVG image is a heavy call.

For 90% of the SVG content out there, it'd probably be faster to parse 
and draw the SVG via Canvas and JS.
Still it's a hell of a lot nicer to load it via <img> tag.

I'd just assumed that <img src="pic.svg" /> was loaded off-thread / 
async much like <img> calls.

There's nothing that gets carried from the document to the <img> other 
than the width/height, which I believe is carried through.
Which is a good thing, of course.


-Charles
Received on Tuesday, 15 May 2012 01:16:17 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:52 GMT