164848 2016-11-16 17:49:35 -0800 Web Inspector: console messages should include async stack trace if available 2019-02-14 14:52:13 -0800 1 1 1 Unclassified WebKit Web Inspector WebKit Nightly Build All All NEW InRadar P2 Normal --- 163230 1 mattbaker webkit-unassigned hi inspector-bugzilla-changes webkit-bug-importer oldest_to_newest 1252146 0 mattbaker 2016-11-16 17:49:35 -0800 Summary: Console messages should include async stack trace if available. When console.trace, console.error, etc, are called from an asynchronous callback the call stack shown the console should include async frames in addition to the standard call frames. Note: Inspector::Protocol::Console::ConsoleMessage already has a stackTrace property, which is currently an array of Console::CallFrame. This can be replaced with Console::StackTrace, and a simple check added to LogManager in the frontend: messageWasAdded(target, source, level, text, type, url, line, column, repeatCount, parameters, stackTrace, requestId) { // Called from WebInspector.ConsoleObserver. stackTrace = stackTrace.callFrames ? stackTrace : WebInspector.StackTrace.fromPayload(target, {callFrames: stackTrace}); ... } 1252149 1 mattbaker 2016-11-16 17:50:40 -0800 or rather: let stackTracePayload = stackTrace.callFrames ? stackTrace : {callFrames: stackTrace}; WebInspector.StackTrace.fromPayload(target, stackTracePayload); 1252150 2 webkit-bug-importer 2016-11-16 17:54:31 -0800 <rdar://problem/29301189> 1506388 3 hi 2019-02-14 14:52:13 -0800 The frontend part sounds "easy", but how about the backend part? I think this would be SUPER awesome 😁, especially for protocol tracing.