Re: [whatwg/fetch] More CORB-protected MIME types - safelist-based approach (#721)

@annevk 

> but there is some model where we could tie things to the element doing the requests that would minimize unbounded memory growth

I think this is the right approach. In the case of opaque data, all responses need to come from the same place. The only thing that can assert this is the API that processes the data (eg the `<audio>`). It's the only thing smart enough to know that if the `src` changes, it's requesting a 'new' resource.

Since `<audio>` would need to keep the original response url (and maybe headers) around anyway, it may as well be used for CORB too.

-- 
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/721#issuecomment-470416242