Re: [fetch] Introduce Response.body. (#118) (#128)

> -<p>A <code>Response</code> object's <span title=concept-Body-body>body</span> is its
> -<span title=concept-Response-response>response</span>'s
> -<span title=concept-response-body>body</span>.
> +<p>A <code>Response</code> object also has an associated
> +<dfn title=concept-Response-readable-stream>readable stream</dfn> of type
> +<span title=concept-ReadableStream>ReadableStream</span> which is initially null.
> +
> +<p class = "note no-backref">The type of the associated
> +<span title=concept-Response-readable-stream>readable stream</span> is defined as
> +<span title=concept-ReadableStream>ReadableStream</span>, but it is currently discussed. Depending
> +on the discussion, the type might be changed to <code>ReadableByteStream</code>. Hence the type name
> +is not strictly specified at this moment, though the behavior is specified because
> +<code>ReadableByteStream</code> has all methods and properties which
> +<span title=concept-ReadableStream>ReadableStream</span> has.
> +
> +<p>A <code>Response</code> object also has an associated

Sorry, disturbed is a bit different. It is mostly fine as you defined it, except I think it should probably apply to interface types, not to individual objects. But I guess the spec as it is currently defines them on individual objects, so no need to change that in your patch.

I think locked would be clearer as I suggested though, unless I am missing something.

---
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/fetch/pull/128/files#r39829019