Bug 161170 - NetworkLoadTiming shouldn't be on ResourceResponseBase
Summary: NetworkLoadTiming shouldn't be on ResourceResponseBase
Status: NEW
Alias: None
Product: WebKit
Classification: Unclassified
Component: Page Loading (show other bugs)
Version: WebKit Nightly Build
Hardware: Unspecified Unspecified
: P3 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-08-24 16:02 PDT by Johan K. Jensen
Modified: 2017-02-10 12:01 PST (History)
3 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Johan K. Jensen 2016-08-24 16:02:46 PDT 
Don't save the NetworkLoadTiming object on the ResourceResponse, as it gets saved to the cache and never used when fetching from the cache.
Comment 1 Joseph Pecoraro 2017-02-10 12:01:26 PST 
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.