W3C home > Mailing lists > Public > public-webapps@w3.org > April to June 2011

Re: [FileAPI] Updates to FileAPI Editor's Draft

From: Jian Li <jianli@chromium.org>
Date: Tue, 7 Jun 2011 10:43:51 -0700
Message-ID: <BANLkTikxSteoHvZxRtkcGLX3aGp_OezrHVkiVAKNpnD3uSF9qQ@mail.gmail.com>
To: "arun@mozilla.com" <arun@mozilla.com>
Cc: Web Applications Working Group WG <public-webapps@w3.org>
I have a couple questions regarding abort behavior.

   - If the reading is completed and the loadend event has been fired, do we
   want to fire loadend event again when abort() method is called?
   - Do we want to reset error to null or leave it intact when abort()
   method is called?

Thanks,

Jian

On Wed, May 11, 2011 at 3:49 PM, Arun Ranganathan <arun@mozilla.com> wrote:

> The Editor's Draft of the FileAPI -- http://dev.w3.org/2006/webapi/**
> FileAPI/ <http://dev.w3.org/2006/webapi/FileAPI/> -- has had some updates.
>  These are the notable changes:
>
> 1. Blob.slice behavior has changed to more closely match
> String.prototype.slice from ECMAScript (and Array.prototype.slice
> semantically).  I think we're the first host object to have a slice outside
> of ECMAScript primitives; some builds of browsers have already
> vendor-prefixed slice till it becomes more stable (and till the new behavior
> becomes more diffuse on the web -- Blob will soon be used in the Canvas API,
> etc.).  I'm optimistic this will happen soon enough.  Thanks to all the
> browser projects that helped initiate the change -- the consistency is
> desirable.
>
> 2. The read methods on FileReader raise a new exception --
> OperationNotAllowedException -- if multiple concurrent reads are invoked.  I
> talked this over with Jonas; we think that rather than reuse DOMException
> error codes (like INVALID_STATE_ERR), these kinds of scenarios should throw
> a distinct exception.  Some things on the web (as in life) are simply not
> allowed.  It may be useful to reuse this exception in other places.
>
> 3. FileReader.abort( ) behavior has changed.
>
> 4. There is a closer integration with event loops as defined by HTML.
>
> For browser projects with open bug databases, I'll log some bugs based on
> test cases I've run on each implementation.  A few discrepancies exist in
> implementations I've tested; for instance, setting FileReader.result to the
> empty string vs. setting it to null, and when exceptions are thrown vs. use
> of the error event.
>
> Feedback encouraged!  Draft at http://dev.w3.org/2006/webapi/**FileAPI/<http://dev.w3.org/2006/webapi/FileAPI/>
>
> -- A*
>
>
>
>
Received on Tuesday, 7 June 2011 17:44:37 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:45 GMT