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

Re: Not making partial result available during FileReader.readAsText()?

From: Michael Nordman <michaeln@google.com>
Date: Fri, 9 Apr 2010 17:49:40 -0700
Message-ID: <o2vfa2eab051004091749x64817e39n99a1980c66f9ca90@mail.gmail.com>
To: Jian Li <jianli@chromium.org>
Cc: Web Applications Working Group WG <public-webapps@w3.org>
Seems pretty clear from the snippet you provided, it says you SHOULD provide
partially decoded results in the result attribute as progress is made.

On Thu, Apr 8, 2010 at 8:31 PM, Jian Li <jianli@chromium.org> wrote:

> For FileReader.readAsText, the spec seems to allow partial file data being
> decoded and saved in the result attribute when progress event is fired:
> Make progress notifications. As the bytes from the fileBlob argument are
> read, user agents SHOULD ensure that on getting, the result attribute
> returns partial file data representing the number of bytes currently loaded
> (as a fraction of the total) [ProgressEvents], decoded in memory according
> to the encoding determination.
> The partial file data read so far might not get decoded completely. Could
> we choose not to decode the partial result till we retrieve all the data,
> just like what FileReader.readAsDataURL does?
Received on Saturday, 10 April 2010 00:50:10 UTC

This archive was generated by hypermail 2.3.1 : Friday, 27 October 2017 07:26:24 UTC