> 5. The cache manifest functionality (which we are using to cache all the MIMES) > is very very touchy. One small mistake causes an error and nothing works. The > information provided to the developer one 'what went wrong' is meager at best. > Not really Apples fault, but these WebKit guys need to get serious on this stuff. > Getting the cache manifest stuff right was easily 60%-70% of our issues. You see > a lot of demos on 'simple' applications out there but no one ever gets complex > with their examples." The developer would like a way to see which resources are NOT included in the manifest for a given page load. Sounds like a great idea. Maybe related to bug 41635, provide a filter in the Resources Panel for Resources that were not Application Cache loaded?
<rdar://problem/19281543>