- From: Ian Hickson <ian@hixie.ch>
- Date: Wed, 31 Mar 2010 18:59:46 +0000 (UTC)
On Wed, 31 Mar 2010, Anne van Kesteren wrote: > On Tue, 30 Mar 2010 15:09:49 -0700, Ian Hickson <ian at hixie.ch> wrote: > > On Tue, 30 Mar 2010, Jonas Sicking wrote: > > > Personally my guess it's more likely that they really wanted to. > > > > I have no idea which is more likely. The only use case I'm aware of is > > passing an <img> in, and for that there isn't really a fallback position, > > so it doesn't matter if we send null or throw an exception. > > Isn't the fallback there to draw the <img> on a <canvas> and then extract an > ImageData object and pass that through to the worker? For the use cases that were mentioned -- rotating or resizing an image -- it's actually slower to do it that way than just to do it on the main thread. (I expect for that use case we'll just add a dedicated API for async batch resizing and rotating of images.) -- Ian Hickson U+1047E )\._.,--....,'``. fL http://ln.hixie.ch/ U+263A /, _.. \ _\ ;`._ ,. Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
Received on Wednesday, 31 March 2010 11:59:46 UTC