3 ms·
It's notable that appcache is now deprecated [0] It's been replaced by Service Workers, but those can get reallly hard to deal with if they start caching thems
by Syrup-tan 10y ago
It's notable that appcache is now deprecated [0]
It's been replaced by Service Workers, but those can get reallly hard to deal with if they start caching themselves (!)
Chrome's devtools has ways to delete old service workers and such, but I've found that on Firefox it's next to impossible to debug.
[0] https://developer.mozilla.org/en-US/docs/Web/HTML/Using_the_application_cache https://developer.mozilla.org/en-US/docs/Web/HTML/Using_the_...
- stqism 10y agoIt's also notable that service worker adoption is only half way at best, whereas appcache is easier to deploy and supported in far more browsers. Not to say service workers aren't the future, but implementing partially adopted features in web pages is poor practice. http://caniuse.com/#feat=serviceworkers http://caniuse.com/#feat=serviceworkers
- Klathmon 10y agoWe are aware and are ready to switch to a service-worker and appcache hybrid when that time comes that appcache is going to be removed. But until then we wanted to keep it simple. Especially during development we don't want to have to deal with differences in SW and appcache.