- From: Ben Kelly <notifications@github.com>
- Date: Fri, 09 Jun 2017 07:23:40 -0700
- To: w3c/ServiceWorker <ServiceWorker@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Friday, 9 June 2017 14:24:15 UTC
> The Cache API is just part of origin storage, so I wouldn't expect the cache API to be removed. Sure, but does this solve the use case of "I tested this on localhost ages ago and I have a bunch of unexpected state on localhost messing up my localhost today"? Still, it would be nice to fix the orphaned update case as that uses actually CPU, bandwidth, etc on real sites today. -- 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/204#issuecomment-307402793
Received on Friday, 9 June 2017 14:24:15 UTC