Index: third_party/WebKit/Source/core/timing/PerformanceResourceTiming.cpp |
diff --git a/third_party/WebKit/Source/core/timing/PerformanceResourceTiming.cpp b/third_party/WebKit/Source/core/timing/PerformanceResourceTiming.cpp |
index bc8441f93083ed1450207b77a167a1a936e177f3..70d1504f03268d288bd441b4722021d5c11125a0 100644 |
--- a/third_party/WebKit/Source/core/timing/PerformanceResourceTiming.cpp |
+++ b/third_party/WebKit/Source/core/timing/PerformanceResourceTiming.cpp |
@@ -49,6 +49,38 @@ static double monotonicTimeToDOMHighResTimeStamp(double timeOrigin, |
} |
PerformanceResourceTiming::PerformanceResourceTiming( |
panicker
2016/11/02 20:12:37
why are 2 ctors necessary?
sunjian
2016/11/04 01:12:39
Because in NavigationTiming's case, there isn't a
|
+ const AtomicString& initiatorType, |
+ double timeOrigin, |
+ ResourceLoadTiming* timing, |
+ double lastRedirectEndTime, |
+ double finishTime, |
+ unsigned long long transferSize, |
+ unsigned long long encodedBodyLength, |
+ unsigned long long decodedBodyLength, |
+ bool didReuseConnection, |
+ bool allowTimingDetails, |
+ bool allowRedirectDetails, |
+ const String& name, |
+ const String& entryType, |
+ double startTime) |
+ : PerformanceEntry( |
+ name, |
+ entryType, |
+ monotonicTimeToDOMHighResTimeStamp(timeOrigin, startTime), |
+ monotonicTimeToDOMHighResTimeStamp(timeOrigin, finishTime)), |
+ m_initiatorType(initiatorType), |
+ m_timeOrigin(timeOrigin), |
+ m_timing(timing), |
+ m_lastRedirectEndTime(lastRedirectEndTime), |
+ m_finishTime(finishTime), |
+ m_transferSize(transferSize), |
+ m_encodedBodySize(encodedBodyLength), |
+ m_decodedBodySize(decodedBodyLength), |
+ m_didReuseConnection(didReuseConnection), |
+ m_allowTimingDetails(allowTimingDetails), |
+ m_allowRedirectDetails(allowRedirectDetails) {} |
+ |
+PerformanceResourceTiming::PerformanceResourceTiming( |
const ResourceTimingInfo& info, |
double timeOrigin, |
double startTime, |