- From: Jake Archibald <notifications@github.com>
- Date: Tue, 04 Jul 2017 09:23:47 +0000 (UTC)
- To: whatwg/fetch <fetch@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Tuesday, 4 July 2017 09:24:21 UTC
@annevk I can write tests for the cases that must produce a network error. Eg returning a ranged response to a request that didn't have a range header. Aside from that, given that the intent is to *prevent* script-created no-cors requests with range headers, it might not be possible to automate the tests. Seeking an audio element should produce enough range requests for testing, but the browser doesn't have to make range requests to be spec-compliant. What's best for me to do next? Make a couple of tests for this PR, or start on the HTML changes? -- 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-312829291
Received on Tuesday, 4 July 2017 09:24:21 UTC