AppCache has the potential to benefit many websites, not only in offline scenarios but also on the performance ground. And yet, developers have struggled to use it in their projects because of the initial implementation quirks, the lack of documentation and tooling.
Now that the implementation and documentation parts are good enough, it’s time to get rid of the next papercuts. I gathered an initial list of those little things that could be fixed or improved to make the AppCache useful and convenient:
- it should be possible to exclude the html file associated with the manifest from the cache,
- it should be possible to cache resources from other origins on https too,
- Firefox should stop asking for user permission and let developers see what’s in the AppCache.
What would you add to this list?
Leave a comment, and I’ll make sure the feedback is heard by Mozilla and Google engineers.