W3C home > Mailing lists > Public > public-wicg@w3.org > August 2015

Re: Hello & a proposal

From: Ashley Gullen <ashley@scirra.com>
Date: Tue, 25 Aug 2015 13:45:27 +0100
Message-ID: <CAABs73hcxA8q_EqsO5jZRFaHO_pzBgem795a+7e2mm3yqDSMOA@mail.gmail.com>
To: Alex Russell <slightlyoff@google.com>
Cc: Marcos Caceres <marcos@marcosc.com>, public-wicg@w3.org
On 24 August 2015 at 20:29, Alex Russell <slightlyoff@google.com> wrote:

> Yeah, read the examples before sending my message. The argument for why
> these operations need to be synchronous isn't clearly presented (this looks
> and smells like I/O w/o a justified blocking behvaior, something we
> generally don't want). I was hoping the authors would outline their
> thinking in a document that isn't just spec + examples.
>

I'm not sure what you're getting at here. Currently JS only provides a
synchronous API for image conversions through canvas, so the examples
demonstrate how it's currently done synchronously, and then propose
asynchronous methods to do the same. What aspect of that needs to be more
clearly presented?





>
> On Mon, Aug 24, 2015 at 11:31 AM, <marcos@marcosc.com> wrote:
>
>>
>>
>>
>>
>> On August 24, 2015 at 2:28:30 PM, Alex Russell (slightlyoff@google.com)
>> wrote:
>> > Is there an explainer document for this proposal somewhere?
>>
>> Not yet, no (Bug #1!:)). But the examples in the spec illustrate the use
>> case.
>>
>> See:
>> https://www.scirra.com/labs/specs/imagedata-conversion-extensions.html
>>
>>
>>
>>
>
Received on Tuesday, 25 August 2015 12:45:59 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 25 August 2015 12:46:00 UTC