- From: Anne van Kesteren <notifications@github.com>
- Date: Sat, 16 Mar 2019 02:48:32 -0700
- To: w3c/FileAPI <FileAPI@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
- Message-ID: <w3c/FileAPI/pull/117/review/215308760@github.com>
annevk commented on this pull request.
> +It must return the result of [=getting a stream for a Blob=] for the [=context object=].
+
+To <dfn lt="get a stream for a Blob|getting a stream for a Blob">get a stream for a {{Blob}}</dfn>
+|blob|, run the following steps:
+
+1. Let |stream| be the result of [=construct a ReadableStream object|constructing=] a
+ {{ReadableStream}} object.
+1. Return |stream| and run the following steps [=in parallel=]:
+ 1. While not all bytes of |blob| have been read:
+ 1. Let |bytes| be the byte sequence that results from reading a [=chunk=] from |blob|.
+ 1. If a [=file read error=] occured while reading |bytes|, [$ReadableStream/error$]
+ |stream| with a [=failure reason=] and abort these steps.
+ 1. [=ReadableStream/Enqueue=] |bytes| into |stream|.
+
+ Issue: We need to specify more concretely what reading from a Blob actually does, and what
+ possible errors can happen.
Ah sorry, see step 13 of https://fetch.spec.whatwg.org/#http-network-fetch. It basically waits for a number of bytes to arrive and then enqueues a Uint8Array. That's probably what you want to mimic to some extent, until there's better infra.
--
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/117#discussion_r266196163
Received on Saturday, 16 March 2019 09:48:53 UTC