Bug 202022 – Web Inspector: unexpected order of entries in the network tab when navigating with 'preserve log'

• Component: Web Inspector
• Status: NEW

[Konrad Dzwinel]

Created attachment 379195 [details]
Screenshot from the network tab showing mixed up requests from two navigations.

Steps to reproduce:
1. Open Web Inspector
2. Go to the network tab
3. Clear log and enable 'Preserve Log' option
4. Navigate to https://duckduckgo.com/ducks
5. Click on any of the search results
6. Let the result page load

Expected result:
Network tab shows duckduckgo.com requests, from the first navigation, at the top and non-duckduckgo.com requests, from the second navigation, below them.

Actual result:
Requests from first and second navigation are mixed up.

Notes:
- this is reproducible in stable (13.0.1) and TP (92)

[Radar WebKit Bug Importer]

<rdar://problem/55545771>

[Joseph Pecoraro]

This appears to only be an issue on cross origin loads, which is when WebKit process swaps.

In that case time the new process starts recording at zero again, and the frontend doesn't account for it.

Fixing this is likely to be a little tricky.

---

Perhaps we should just move to an absolute time world instead of the stopwatch. I'm not sure the stopwatch has ever really gained us much. If I recall correctly, the idea behind the Stopwatch was that you could pause in the debugger (and stop the stopwatch) then continue (and resume the stopwatch) and various inspector timelines (Network and Timelines) would appear as if the pause never even happened. Which is cool in theory but probably doesn't actually matter.