<html>
<head>
<base href="https://bugs.webkit.org/" />
</head>
<body><table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>Bug ID</th>
<td><a class="bz_bug_link
bz_status_NEW "
title="NEW - [NavigationTiming] requestStart, responseStart before navigationStart"
href="https://bugs.webkit.org/show_bug.cgi?id=168055">168055</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>[NavigationTiming] requestStart, responseStart before navigationStart
</td>
</tr>
<tr>
<th>Classification</th>
<td>Unclassified
</td>
</tr>
<tr>
<th>Product</th>
<td>WebKit
</td>
</tr>
<tr>
<th>Version</th>
<td>Safari 10
</td>
</tr>
<tr>
<th>Hardware</th>
<td>All
</td>
</tr>
<tr>
<th>OS</th>
<td>All
</td>
</tr>
<tr>
<th>Status</th>
<td>NEW
</td>
</tr>
<tr>
<th>Severity</th>
<td>Normal
</td>
</tr>
<tr>
<th>Priority</th>
<td>P2
</td>
</tr>
<tr>
<th>Component</th>
<td>Platform
</td>
</tr>
<tr>
<th>Assignee</th>
<td>webkit-unassigned@lists.webkit.org
</td>
</tr>
<tr>
<th>Reporter</th>
<td>nic@nicj.net
</td>
</tr></table>
<p>
<div>
<pre>Hi,
We're seeing infrequent cases where NavigationTiming timestamps such as requestStart and responseStart are happening prior to navigationStart.
Here's one example:
Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_1) AppleWebKit/602.2.14 (KHTML, like Gecko) Version/10.0.1 Safari/602.2.14
navigation.type 0 // navigation
redirectStart 0
redirectEnd 0
requestStart 1486654516288 // incorrect: before navigationStart
responseStart 1486654516819 // incorrect: before navigationStart
navigationStart 1486654517415
fetchStart 1486654517415
domainLookupStart 1486654517415
domainLookupEnd 1486654517415
connectStart 1486654517415
connectEnd 1486654517415
domLoading 1486654518045
responseEnd 1486654518085
domInteractive 1486654518312
domContentLoadedEventStart 1486654518312
domContentLoadedEventEnd 1486654518316
domComplete 1486654518596
loadEventStart 1486654518599
Here's a second example:
Mozilla/5.0 (iPhone; CPU iPhone OS 10_2_1 like Mac OS X) AppleWebKit/602.4.6 (KHTML, like Gecko) Version/10.0 Mobile/14D27 Safari/602.1
navigation.type 0 // navigation
redirectStart 0
redirectEnd 0
requestStart 1486647959659 // incorrect: before navigationStart
navigationStart 1486647959737
fetchStart 1486647959737
domainLookupStart 1486647959737
domainLookupEnd 1486647959737
connectStart 1486647959737
connectEnd 1486647959737
responseStart 1486647959828
responseEnd 1486647959969
domLoading 1486647959971
domInteractive 1486647962594
domContentLoadedEventStart 1486647962710
domContentLoadedEventEnd 1486647962985
domComplete 1486647967189
loadEventStart 1486647967192
This doesn't happen frequently -- in one data set I'm looking at, it's 3 beacons out of 254,357.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>