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

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

From: Jian Li <jianli@chromium.org>
Date: Fri, 9 Apr 2010 18:33:12 -0700
Message-ID: <k2ka95818c31004091833h41e26385jb969c6c38c710854@mail.gmail.com>
To: Michael Nordman <michaeln@google.com>
Cc: Web Applications Working Group WG <public-webapps@w3.org>
Should we really want to support this? As I know, FF 3.6 does not support
this in its current FileReader implementation. I just want to understand if
there is a strong need for this.

On Fri, Apr 9, 2010 at 5:49 PM, Michael Nordman <michaeln@google.com> wrote:

> 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 01:33:41 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:13:06 UTC