<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 - Web Inspector: resources don't show in resources/debugger sidebar after navigating inspected page back"
href="https://bugs.webkit.org/show_bug.cgi?id=158404">158404</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>Web Inspector: resources don't show in resources/debugger sidebar after navigating inspected page back
</td>
</tr>
<tr>
<th>Classification</th>
<td>Unclassified
</td>
</tr>
<tr>
<th>Product</th>
<td>WebKit
</td>
</tr>
<tr>
<th>Version</th>
<td>WebKit Nightly Build
</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>Web Inspector
</td>
</tr>
<tr>
<th>Assignee</th>
<td>webkit-unassigned@lists.webkit.org
</td>
</tr>
<tr>
<th>Reporter</th>
<td>bburg@apple.com
</td>
</tr>
<tr>
<th>CC</th>
<td>bburg@apple.com, graouts@webkit.org, joepeck@webkit.org, mattbaker@apple.com, nvasilyev@apple.com, timothy@apple.com, webkit-bug-importer@group.apple.com
</td>
</tr></table>
<p>
<div>
<pre>STEPS TO REPRODUCE:
1. Go to attached page
2. Open inspector to Resources or Debugger tab.
3. Navigate the inspected page away to another page
4. Press the back button or evaluate window.history.back()
EXPECTED:
Main resource appears in sidebar, along with any resources that were downloaded or failed when the page was loaded
ACTUAL:
Nothing appears in the sidebar at all
NOTES:
This appears to be related to the back-forward cache. If this is a cache hit, then WebCore will not tell the frontend about any new resource loads because it doesn't perform any loads at all to redisplay the page. If it's a miss, then it works fine because we have to re-download or revalidate resources.
I'm not sure how we should fix this.
- We shouldn't disable the back-forward cache while inspecting for performance reasons. That also be bad because it would make it impossible to debug problems that web content may have related to the back-forward cache (like page visibility and throttling).
- One option is to tell the inspector about the navigation type (specifically, whether it hit the back-forward cache), and have the frontend keep around past resource trees until they are purged from the back-forward cache. I don't think the backend can re-send this data, since the original request data is probably not kept around after loading a resource finishes.</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>