Summary: | [Resource Timing] El Capitan NetworkLoadTiming values are sometimes jumbled | ||
---|---|---|---|
Product: | WebKit | Reporter: | Joseph Pecoraro <joepeck> |
Component: | WebCore Misc. | Assignee: | Joseph Pecoraro <joepeck> |
Status: | RESOLVED WONTFIX | ||
Severity: | Normal | CC: | achristensen, ap, beidson, joepeck, mcatanzaro, webkit-bug-importer, youennf |
Priority: | P2 | Keywords: | InRadar |
Version: | WebKit Nightly Build | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Bug Depends on: | 175674 | ||
Bug Blocks: |
Description
Joseph Pecoraro
2017-02-15 23:12:27 PST
Reopening, sorry for closing it. The tests marked against this bug are passing for GTK+ now, see bug #175674. But I don't know about other platforms. It's worth checking if this is still a problem on El Capitan. It's likely this is something that changed in CFNetwork between El Capitan and Sierra, and won't be fixed in WebKit anyways. (In reply to Alex Christensen from comment #3) > It's likely this is something that changed in CFNetwork between El Capitan > and Sierra, and won't be fixed in WebKit anyways. Correct. The values from CFNetwork were jumbled. Ultimately that got addressed in Sierra when CFNetwork introduced NSURLSessionTaskTransactionMetrics and improved and corrected handling of all the loading metrics, very much in-line with the W3C Resource Timing data. Since that data comes from a component underneath WebKit I think its unlikely to get addressed for an older OS. As a result, El Capitan won't have ResourceTiming enabled but newer OSes will. |