Re: [w3c/ServiceWorker] Change add(request) and addAll(requests) behavior (e2a6d18)

Clearly the documentation could be improved, but we did try to update it.  See:

https://bugzilla.mozilla.org/show_bug.cgi?id=1244764#c19

And the "Exception" section in these two pages:

https://developer.mozilla.org/en-US/docs/Web/API/Cache/add
https://developer.mozilla.org/en-US/docs/Web/API/Cache/addAll

Personally I'd be more inclined to remove `add()` and `addAll()` rather than try to make them magically work better for opaque responses.  In hindsight I think it was a mistake to try to add a convenience fetch+put operation into the platform so soon.

I also think people should probably avoid opaque responses in any kind of cache-first scenario.  You just have no way to tell if the resource loaded or not.  If you want to use a cache-first model you really need to get the resource served with CORS.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/ServiceWorker/commit/e2a6d18647b97707c7a571163eef7838f82ca611#commitcomment-18735022