Re: [whatwg/fetch] Fetch Timing Info's end time is set to a relative timestamp, when it should be the original captured unsafe current time (Issue #1812)

annevk left a comment (whatwg/fetch#1812)

I think the bug is Resource Timing doing duplicate/incorrect work. I helped design the Fetch aspects of this feature and did not want Fetch to leak any unsafe timing.

cc @noamr 

-- 
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/fetch/issues/1812#issuecomment-2703541654
You are receiving this because you are subscribed to this thread.

Message ID: <whatwg/fetch/issues/1812/2703541654@github.com>