Re: [whatwg/fetch] Fix body handling on the Request constructor (#458)

annevk commented on this pull request.



>     <li>
-    <p>Let <var>reader</var> be the result of <a lt="get a reader" for=ReadableStream>getting a reader</a>
-    from <var>dummyStream</var>.
-    <p class="note no-backref">This operation will not throw an exception.
-
-   <li>
-    <p><a lt="read all bytes" for=ReadableStream>Read all bytes</a> from
-    <var>dummyStream</var> with <var>reader</var>.
-    <p class="note no-backref">This operation makes <var>dummyStream</var> disturbed.
+    <p>Let <var>rs</var> bs a {{ReadableStream}} object from which one can read the exactly
+    same data as one could read from <var>inputBody</var>'s <a for=body>stream</a>.
+    <p class="note no-backref">This will be specified more precisely once
+    <a href=https://streams.spec.whatwg.org/#ts-model>transform stream</a> and
+    <a href=https://streams.spec.whatwg.org/#pipe-chains>piping</a> are precisely defined.
+    This makes <var>inputBody</var>'s <a for=body>stream</a> <a for=ReadableStream>locked</a> and
+    <a for=ReadableStream>disturbed</a> immediately.

I suggest we file an issue against Fetch to track this. And make this a class=XXX rather than a note.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/fetch/pull/458#pullrequestreview-17437325

Received on Thursday, 19 January 2017 11:44:31 UTC