Bug 41640
| Summary: | Web Inspector: Indicate Which Loaded Resources Were Not in an Application Cache Manifest | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Joseph Pecoraro <joepeck> |
| Component: | Web Inspector | Assignee: | Nobody <webkit-unassigned> |
| Status: | UNCONFIRMED | ||
| Severity: | Normal | CC: | bweinstein, graouts, inspector-bugzilla-changes, jonowells, keishi, pfeldman, pmuellr, rik, webkit-bug-importer, yurys |
| Priority: | P2 | Keywords: | InRadar |
| Version: | 528+ (Nightly build) | ||
| Hardware: | All | ||
| OS: | All | ||
Joseph Pecoraro
> 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?
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Radar WebKit Bug Importer
<rdar://problem/19281543>