<html>
<head>
<base href="https://bugs.webkit.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - Web Inspector: Activity Viewer does not update on "clear all console messages""
href="https://bugs.webkit.org/show_bug.cgi?id=144681#c4">Comment # 4</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - Web Inspector: Activity Viewer does not update on "clear all console messages""
href="https://bugs.webkit.org/show_bug.cgi?id=144681">bug 144681</a>
from <span class="vcard"><a class="email" href="mailto:tobi+bugzilla@basecode.de" title="tobi+bugzilla@basecode.de">tobi+bugzilla@basecode.de</a>
</span></b>
<pre>LogManager listens on "Console.messagesCleared" events from Backend. A typical stack of events looks like this on a page reload:
- load page that contains a console.log("test")
- "WebInspector.ConsoleObserver.messageAdded" // from Backend, prints "test"
- reload page
- "WebInspector.ConsoleObserver.messagesCleared" // from Backend
- "WebInspector.Frame.Event.MainResourceDidChange" // from ?, indicates "session start"
- "WebInspector.ConsoleObserver.messageAdded" // from Backend, prints "test"
- "WebInspector.ConsoleObserver.messagesCleared" // from Backend, why??
Conclusion
The former "messagesCleared" can be instrumented to clear on reload or not.
The latter "messagesCleared" breaks our logic and should be avoided.</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>