Fix secureConnectionStart when connection is reused

Per ResourceTiming spec, if a connection is reused then secureConnectionStart must return fetchStart, not 0. Bug: 404501 Change-Id: Ica208c98cfea0afa9dd22e4edc83cc3c430c219f
web-platform-tests · Dec 7, 2018 · 0c15d1d · 0c15d1d
1 parent 6a51887
commit 0c15d1d
Showing 1 changed file with 4 additions and 0 deletions.
diff --git a/resource-timing/resource_connection_reuse.html b/resource-timing/resource_connection_reuse.html
@@ -41,6 +41,10 @@
         const entry = entries[1];
         test_equals(entry.fetchStart, entry.connectStart, 'connectStart and fetchStart should be the same');
         test_equals(entry.fetchStart, entry.connectEnd, 'connectEnd and fetchStart should be the same');
+        test_equals(entry.fetchStart, entry.secureConnectionStart, 'secureConnectStart and fetchStart should be the same');
+        test_equals(entry.fetchStart, entry.domainLookupStart, 'domainLookupStart and fetchStart should be the same')
+        test_equals(entry.fetchStart, entry.domainLookupEnd, 'domainLookupEnd and fetchStart should be the same')
+
     }
 
     done();