W3C home > Mailing lists > Public > public-houdini@w3.org > February 2015

Re: Image decoding off the main thread

From: Simon Pieters <simonp@opera.com>
Date: Wed, 11 Feb 2015 13:25:05 +0400
To: "Dean Jackson" <dino@apple.com>, "Ryan Seddon" <seddon.ryan@gmail.com>
Cc: public-houdini@w3.org
Message-ID: <op.xtv7f3anidj3kv@simons-macbook-pro.local>
On Wed, 11 Feb 2015 13:42:33 +0400, Ryan Seddon <seddon.ryan@gmail.com>  
wrote:

> Looks like WebKit, and I assume Blink, already put image decoding of
> background images off the main thread. [1]
>
> As a developer I would love to see this as an attribute on <img>, would
> this include <picture> as well?

Since it's <img> that does the "work", generally everything should work  
the same for <picture>.

> [1] https://bugs.webkit.org/show_bug.cgi?id=99790
>
> On Wed, Feb 11, 2015 at 8:09 PM, Dean Jackson <dino@apple.com> wrote:
>
>> Three days late, but I finally thought of something I wish I'd proposed  
>> at
>> the meeting: image decoding on a background thread.
>>
>> For this I guess we'd need some attribute on IMG/Image/HTMLImageElement
>> that would indicate that the main thread doesn't have to decode this  
>> image.

Why do we need an attribute?

>> I'm not sure if we need a new "ready" event, or just assume that "load"
>> means loaded and decoded.

"load" already means that, I think. Or possibly completely loaded and  
decoded enough to know the image's dimensions. Why would we need a new  
event?

-- 
Simon Pieters
Opera Software
Received on Wednesday, 11 February 2015 12:25:37 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 11 February 2015 15:47:05 UTC