Re: [whatwg/fetch] Using fetch in other standards (#1314)

@ricea approved this pull request.

lgtm

> @@ -7828,6 +7828,63 @@ resource — for non-<a>CORS requests</a> as well as <a>CORS
 requests</a> — and do not use `<code>Vary</code>`.
 
 
+<h2 id=fetch-elsewhere class=no-num>Fetch elsewhere</h2>

When I went to look for this text in the preview, I didn't immediately find "Fetch elsewhere" Maybe a more boring title like "Using Fetch from other standards" would be better?

> +  <a>byte sequence</a>. This is useful for standards that wish to operate on the entire
+  <a for=/>response</a>'s <a for=response>body</a>, of which the result of reading it is supplied as
+  second argument.
+
+  <p>It might be surprising that a <a for=/>network error</a> will have null as second argument.
+
+  <p class=warning>A standard that uses this argument cannot operate on <a for=/>response</a>'s
+  <a for=response>body</a> itself as providing this argument will cause it to be read and it can be
+  read only once.
+
+ <dt><a for=fetch><i>processResponseDone</i></a>
+ <dd><p>Takes an algorithm that will be passed a <a for=/>response</a>. Indicates the network is
+ done transmitting the response. This does not read <a for=/>response</a>'s
+ <a for=response>body</a>.
+
+ <dt><a for=fetch><i>useParallelQueue</i></a>

I assume this defaults to false. Do you need to say so explicitly?

-- 
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/1314#pullrequestreview-774730222