Re: [whatwg/fetch] Allow range header to be set by APIs (#560)

@foolip 

> Media fragments `#t=30,60` as actually implemented doesn't actually interact with the fetch layer at all. Rather, you just try to load the file and then seek to time offset 30. 

`new Audio("/path/to/media#t=30,60")` makes range request, yes? Being a novice at interacting with specification criteria, had the concept of implementing the feature 

```
fetch("/path/to/media#t=30,60"
, {context:HTMLMediaElement}
}) // consistent with new Audio() range request 
.then(response => response.blob())
.then(({destination, blob}) => {
  // do stuff with `Blob` having time slice of `30,60`, or full file with `destination` time slice set to `30,60`
  // `destination` : i.e.g., `<audio>`, `Audio`, `AudioContext`, `<video>`, `MediaSource`, `MediaStream`
})
```

-- 
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/560#issuecomment-313252126