W3C home > Mailing lists > Public > whatwg@whatwg.org > January 2010

[whatwg] HTMLCanvasElement.toFile()

From: Jonas Sicking <jonas@sicking.cc>
Date: Thu, 7 Jan 2010 15:14:40 -0800
Message-ID: <63df84f1001071514h55ff5b3cn3bccf25da7a40be0@mail.gmail.com>
On Thu, Jan 7, 2010 at 2:27 PM, Jo?o Eiras <joaoe at opera.com> wrote:
>
>>> This function takes the same arguments as toDataURL(), plus an
>>> additional 'name' argument. It produces the same result as
>>> toDataURL(), except that it returns the result as a File object rather
>>> than as a data-url encoded string. This can then be directly sent
>>> using XMLHttpRequest.
>>
>> I think it would make more sense to have an actual type for binary data
>> (for example along the lines of my proposal on public-script-coord and
>> es-discuss) and enable getting one from <canvas> and sending via XHR.
>
> How about just overloading xhr.send() to handle a <canvas> element ?

I'm reluctant to overload the meaning of sending an Element object.
When a Document is passed to xhr.send() we already serialize that
document into markup, it seems likely to me that in the future we'll
want to do the same thing for Elements.

/ Jonas
Received on Thursday, 7 January 2010 15:14:40 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 16:59:20 UTC