- From: Robert O'Callahan <robert@ocallahan.org>
- Date: Thu, 11 Feb 2016 12:24:48 +1300
- To: Justin Novosad <junov@google.com>
- Cc: "whatwg@whatwg.org" <whatwg@whatwg.org>, Gregg Tavares <gman@chromium.org>, Ashley Gullen <ashley@scirra.com>
On Thu, Feb 11, 2016 at 9:27 AM, Justin Novosad <junov@google.com> wrote: > On Wed, Feb 10, 2016 at 2:38 PM, Ashley Gullen <ashley@scirra.com> wrote: > > > ImageBitmap is not useful for getting the data from: it still requires > > synchronous use of a canvas to turn in to an ImageData. I would encourage > > browser vendors to look at my spec proposal to avoid this: > > http://wicg.github.io/img-conversion/ > > > Yes, that is on our radar. We need APIs to move image data without making > so many intermediate copies in RAM. AFAIK, this appears to be a real > problem for image manipulation apps, which tend to quickly run out of RAM. > ImageBitmap partially addresses this, but it does little for apps that need > to do direct image data manipulation. > http://kakukogou.github.io/spec-imagebitmap-extension/ Rob -- lbir ye,ea yer.tnietoehr rdn rdsme,anea lurpr edna e hnysnenh hhe uresyf toD selthor stor edna siewaoeodm or v sstvr esBa kbvted,t rdsme,aoreseoouoto o l euetiuruewFa kbn e hnystoivateweh uresyf tulsa rehr rdm or rnea lurpr .a war hsrer holsa rodvted,t nenh hneireseoouot.tniesiewaoeivatewt sstvr esn
Received on Wednesday, 10 February 2016 23:25:17 UTC