Re: [whatwg/fetch] Allow request/response.blob() to resolve before reading the full stream (#556)

@jakearchibald Range requests is the fix. With `fetch()`, `Request()` having the same implementation as [Media Fragments URI 1.0](https://www.w3.org/TR/media-frags/). Else, `ReadableStream` can already be utilized to append an `ArrayBuffer` to a `SourceBuffer` of `MediaSource` for media playback. Currently, `#t30,50` is stripped from URL passed to `Request()`, `fetch()`. 

The `type` and `destination` portions of the specification (`fetch()`) was confusing to this reader, even though the spec clearly states that those properties are not exposed to JavaScript. Tried to set `type`, `destination` to `"audio"` attempting for `fetch()` `Response` to have same effect as `new Audio("/audio#t=30,50")`, though obviously, this did return expected result; `#t=30,50` is stripped from URL, yes? 

How can we make a `fetch()` request appear to be an `Audio()` request, or, when the response is received by `fetch()`, incorporate the processing model of `Audio()` which gets only the media fragment? 

-- 
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/issues/556#issuecomment-309908979