[Webkit-unassigned] [Bug 158404] New: Web Inspector: resources don't show in resources/debugger sidebar after navigating inspected page back

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Sun Jun 5 15:17:24 PDT 2016


            Bug ID: 158404
           Summary: Web Inspector: resources don't show in
                    resources/debugger sidebar after navigating inspected
                    page back
    Classification: Unclassified
           Product: WebKit
           Version: WebKit Nightly Build
          Hardware: All
                OS: All
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: Web Inspector
          Assignee: webkit-unassigned at lists.webkit.org
          Reporter: bburg at apple.com
                CC: bburg at apple.com, graouts at webkit.org,
                    joepeck at webkit.org, mattbaker at apple.com,
                    nvasilyev at apple.com, timothy at apple.com,
                    webkit-bug-importer at group.apple.com


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()


Main resource appears in sidebar, along with any resources that were downloaded or failed when the page was loaded


Nothing appears in the sidebar at all


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.

You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.webkit.org/pipermail/webkit-unassigned/attachments/20160605/732590e6/attachment.html>

More information about the webkit-unassigned mailing list