- From: Anne van Kesteren <notifications@github.com>
- Date: Thu, 14 Mar 2019 13:29:52 -0700
- To: w3c/FileAPI <FileAPI@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Thursday, 14 March 2019 20:30:13 UTC
annevk commented on this pull request. > +<div algorithm="read operation"> +A {{FileReader}} has an associated <dfn id=readOperation>read operation</dfn> algorithm, +given |blob|, a |type| and an optional |encodingName|, +runs the following steps: + +1. Set the [=context object=]'s {{FileReader/result}} to `null`. +1. Set the [=context object=]'s {{FileReader/error!!attribute}} to `null`. +1. Let |stream| be the result of calling [=get stream=] on |blob|. +1. Let |reader| be the result of [=get a reader|getting a reader=] from |stream|. +1. Let |bytes| by an empty [=byte sequence=]. +1. Let |chunk| be the result of [=read a chunk|reading a chunk=] from |stream| with |reader|. +1. Let |isFirstChunk| be true. +1. [=In parallel=], while true: + 1. Wait for |chunk| to be fulfilled or rejected. + 1. If |chunk| is fulfilled, and |isFirstChunk| is true, + [=queue a task=] to [=fire a progress event=] called {{loadstart}} at the [=context object=]. I think my only argument is consistency with the initial API that had `loadstart`. (And perhaps poor initial review by Mozilla.) -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3c/FileAPI/pull/118#discussion_r265753539
Received on Thursday, 14 March 2019 20:30:13 UTC