Bug 161170
| Summary: | NetworkLoadTiming shouldn't be on ResourceResponseBase | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Johan K. Jensen <jj> |
| Component: | Page Loading | Assignee: | Nobody <webkit-unassigned> |
| Status: | NEW | ||
| Severity: | Normal | CC: | beidson, joepeck, koivisto |
| Priority: | P3 | ||
| Version: | WebKit Nightly Build | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
Johan K. Jensen
Don't save the NetworkLoadTiming object on the ResourceResponse, as it gets saved to the cache and never used when fetching from the cache.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Joseph Pecoraro
This would be great cleanup for Resource Timing.
I think currently it is on ResourceResponse so that it gets serialized with the ResourceResponse from the NetworkProcess to the WebContentProcess in didReceiveResponse.
I'll keep this in mind as I further the Resource Timing implementation.