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

> I wouldn't expect the presence of a service worker to change how the image cache works (as spec'd), or are you talking about something more Firefox specific?

My spec knowledge of image cache is rather weak.  But we can test the following:

Compare these steps in chrome and firefox:

1. Load https://jakearchibald.github.io/service-worker-benchmark/
2. Navigate to http://example.com in the same tab (so process is re-used)
3. Paste https://jakearchibald.github.io/service-worker-benchmark/ in tab URL bar again

In the no service worker installed case step (3) gets:

Chrome: 545ms
Firefox: 174ms

In the empty fetch SW case step (3) gets:

Chrome: 570ms
Firefox: 835ms

Firefox is doing some image caching within the process on navigation, but only if SW is not installed.

-- 
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-290591327