Re: [w3c/ServiceWorker] allow service worker produced resources to be marked as "cachable" (#962)

> However, the above caches are tied to the current document. Chrome's skipping the CSS request between documents, and that does seem odd. My gut feeling is there should be a fetch event here, and whatever cache Chrome is using here should sit behind the service worker.

So we do actually re-use our image cache across documents, but we explicitly disable that when service workers are in play.

It would be nice to support these things, but perhaps the service worker shoudl explictly opt in to it?  Or is the cache-control header enough?

Lets discuss at the face-to-face in april

-- 
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/issues/962#issuecomment-264518907