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

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. In other words, there's no existing behavior beyond byte range requests that fetch needs to explain. (Disclaimer: I haven't read the whole discussion.)

-- 
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-313059591