Searched refs:resourceLoadTimeRelativeToAbsolute (Results 1 – 4 of 4) sorted by relevance
169 return resourceLoadTimeRelativeToAbsolute(dnsStart); in domainLookupStart()184 return resourceLoadTimeRelativeToAbsolute(dnsEnd); in domainLookupEnd()208 return resourceLoadTimeRelativeToAbsolute(connectStart); in connectStart()227 return resourceLoadTimeRelativeToAbsolute(connectEnd); in connectEnd()244 return resourceLoadTimeRelativeToAbsolute(sslStart); in secureConnectionStart()254 return resourceLoadTimeRelativeToAbsolute(timing->sendStart); in requestStart()270 return resourceLoadTimeRelativeToAbsolute(timing->receiveHeadersEnd); in responseStart()383 unsigned long long PerformanceTiming::resourceLoadTimeRelativeToAbsolute(int relativeSeconds) const in resourceLoadTimeRelativeToAbsolute() function in WebCore::PerformanceTiming
83 unsigned long long resourceLoadTimeRelativeToAbsolute(int) const;
13193 (WebCore::PerformanceTiming::resourceLoadTimeRelativeToAbsolute):95561 …(WebCore::Timing::resourceLoadTimeRelativeToAbsolute): Now that responseEnd is set correctly, it c…97314 …(WebCore::Timing::resourceLoadTimeRelativeToAbsolute): Ensure requestTime is in the range of fetch…
32123 (WebCore::PerformanceTiming::resourceLoadTimeRelativeToAbsolute): Use full upper bound.