Re: [whatwg/fetch] CORB: empty response VS erroring out (#727)

Here's the problem:

```js
fetch('https://example.com/whatever', { mode: 'no-cors' }).catch(() => {
  // This smells like a CORB-blocked resource.
});
```

The question is, this is an acceptable data leak?

-- 
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/727#issuecomment-390909731