[Webkit-unassigned] [Bug 148696] New: Web Inspector: Option to preserve logs on console and network tabs

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=148696

            Bug ID: 148696
           Summary: Web Inspector: Option to preserve logs on console and
                    network tabs
    Classification: Unclassified
           Product: WebKit
           Version: Safari 9
          Hardware: All
                OS: Mac OS X 10.11
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: Web Inspector
          Assignee: webkit-unassigned at lists.webkit.org
          Reporter: irae at irae.pro.br
                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

In previous versions of Webkit every time I reloaded the page I would get a dashed line and the console would not clear. This was somewhat useful but for certain scenarios, like when debugging page load issues, it can get very cluttered. In the current Safari 9 beta there is the reverse behavior, either navigating away from the page or reloading the page is clearing the console.

I agree clearing should be the default behavior, but having and option to preserve the logs is specially useful when navigating away from the page and analyzing console.log messages that are happening on the click handlers and onBeforeUnload handlers when present.

This is sometimes also relevant for network messages. Some libraries will fire a network request (user metric libraries, for instance) before letting the user navigate away. In those scenarios I faced very hard to debug problems with Safari, specially when debugging Safari over USB to get actual device results. Would be very helpful to have the Safari WebInspector to hold this data and it's visualizations in memory as an option.

-- 
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/20150902/851651c1/attachment.html>