W3C home > Mailing lists > Public > public-device-apis@w3.org > June 2010

Re: Updates to File API

From: Jian Li <jianli@chromium.org>
Date: Wed, 2 Jun 2010 15:57:53 -0700
Message-ID: <AANLkTilaMaZLeH3aIDnx0Z8zB45owiPsgfGfwXMja63h@mail.gmail.com>
To: Eric Uhrhane <ericu@google.com>
Cc: arun@mozilla.com, Web Applications Working Group WG <public-webapps@w3.org>, public-device-apis <public-device-apis@w3.org>
On Wed, Jun 2, 2010 at 3:48 PM, Eric Uhrhane <ericu@google.com> wrote:

> On Wed, Jun 2, 2010 at 3:44 PM, Arun Ranganathan <arun@mozilla.com> wrote:
> > On 6/2/10 3:42 PM, Eric Uhrhane wrote:
> >>
> >> Arun:
> >>
> >> In the latest version of the spec I see that readAsDataURL, alone
> >> among the readAs* methods, still takes a File rather than a Blob.  Is
> >> that just an oversight, or is that an intentional restriction?
> >>
> >
> > That's intentional; readAsDataURL was cited as useful only in the context
> of
> > File objects.  Do you think it makes sense in the context of random Blob
> > objects?  Does it make sense on slice calls on a Blob, for example?
>
> Sure, why not?  Why would this be limited to File objects?
>
> A File is supposed to refer to an actual file on the local hard drive.
>  A Blob is a big bunch of data that you might want to do something
> with.  There's nothing special about a File when it comes to what
> you're doing with the data.
>
> Just as we moved File.url up to Blob, I think File.readAsDataURL
> belongs there too.
>

And we move type from File to Blob.
Received on Wednesday, 2 June 2010 22:59:17 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 9 May 2012 00:14:10 GMT