- From: Ashley Gullen <ashley@scirra.com>
- Date: Sat, 21 Mar 2015 13:21:39 +0000
- To: Jake Archibald <jaffathecake@gmail.com>
- Cc: WHATWG <whatwg@whatwg.org>, Ian Hickson <ian@hixie.ch>, Rik Cabanier <cabanier@gmail.com>, Robert O'Callahan <robert@ocallahan.org>
Is everyone here aware that currently Google have stated they do not plan to implement toBlob?: https://code.google.com/p/chromium/issues/detail?id=67587 IMO this is the wrong call. We should be favouring blobs over data URLs since they are more efficient (no size bloat, can be requested async like other network resources, no need to copy round very large strings). On 21 March 2015 at 11:19, Jake Archibald <jaffathecake@gmail.com> wrote: > I'd rather we did that by introducing promises to HTMLCanvasElement. > Returning a promise from toBlob is easy, making the callback arg optional > by checking the type of the first arg is hacky but possible (and is done in > js libs). > > On Sat, 21 Mar 2015 10:56 Robert O'Callahan <robert@ocallahan.org> wrote: > > > On Sat, Mar 21, 2015 at 5:45 PM, Rik Cabanier <cabanier@gmail.com> > wrote: > > > >> Ah, OK. I thought we were changing it for both cases. This will cause a > >> lot > >> of confusion... > >> > > > > If we want to keep HTMLCanvasElement and WorkerCanvas in sync, we can. > > > > Rob > > -- > > oIo otoeololo oyooouo otohoaoto oaonoyooonoeo owohooo oioso oaonogoroyo > > owoiotoho oao oboroootohoeoro oooro osoiosotoeoro owoiololo oboeo > > osouobojoeocoto otooo ojouodogomoeonoto.o oAogoaoiono,o oaonoyooonoeo > > owohooo > > osoaoyoso otooo oao oboroootohoeoro oooro osoiosotoeoro,o o‘oRoaocoao,o’o > > oioso > > oaonosowoeoroaoboloeo otooo otohoeo ocooouoroto.o oAonodo oaonoyooonoeo > > owohooo > > osoaoyoso,o o‘oYooouo ofooooolo!o’o owoiololo oboeo oiono odoaonogoeoro > > ooofo > > otohoeo ofoioroeo ooofo ohoeololo. > > >
Received on Saturday, 21 March 2015 13:22:08 UTC