Re: [whatwg/fetch] Cross-Origin Read Blocking (CORB) (#681)

Maybe @anforowicz or Nick Carter can chime in more, but in terms of persisting no-cors to disk, Chrome's implementation is still able to write the response to disk without giving it to the renderer process that made the request.  (I think we're using [DetachableResourceHandler ](https://cs.chromium.org/chromium/src/content/browser/loader/detachable_resource_handler.h)for that, FWIW.)  That may be worth mentioning in the explainer, since I think it matters for preload and ServiceWorkers as well.  Were there other cases you were concerned about?

-- 
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/681#issuecomment-378436039