https://trac.webkit.org/changeset/278391/webkit changed how InspectorNetworkAgent::buildObjectForTiming serializes NetworkLoadMetrics to the inspector protocol. millisecondsSinceFetchStart subtracts fetchStart to get relative values for most of the metrics. In Curl implementation fetchStart is always 0 which results in incorrect values sent over the protocol.
Created attachment 431162 [details] Patch
Don't you need to set redirectStart? Cocoa port does.
It would be great the following WinCairo test failures are fixed. fast/dom/webtiming.html [ Failure ] http/tests/misc/webtiming-cross-origin-redirect.py [ Failure ] http/tests/misc/webtiming-one-redirect.py [ Failure ] http/tests/misc/webtiming-two-redirects.py [ Failure ]
(In reply to Fujii Hironori from comment #2) > Don't you need to set redirectStart? Cocoa port does. I think you are write, I noticed that redirectSart was also missing but decided not to touch it since it was not a part of the regression, can add that too.
Committed r278752 (238713@main): <https://commits.webkit.org/238713@main> All reviewed patches have been landed. Closing bug and clearing flags on attachment 431162 [details].
<rdar://problem/79176779>