[Webkit-unassigned] [Bug 104854] New: Web Inspector: Show which exception causes break on exception.
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Wed Dec 12 15:28:20 PST 2012
https://bugs.webkit.org/show_bug.cgi?id=104854
Summary: Web Inspector: Show which exception causes break on
exception.
Product: WebKit
Version: 528+ (Nightly build)
Platform: All
OS/Version: All
Status: UNCONFIRMED
Severity: Normal
Priority: P2
Component: Web Inspector
AssignedTo: webkit-unassigned at lists.webkit.org
ReportedBy: johnjbarton at chromium.org
CC: keishi at webkit.org, pmuellr at yahoo.com,
pfeldman at chromium.org, yurys at chromium.org,
apavlov at chromium.org, loislo at chromium.org,
vsevik at chromium.org,
web-inspector-bugs at googlegroups.com
The current user experience for break on exception is puzzling: the debugger stops on the line of the error, but gives no information about the error message other than a cryptic <exception> property in Local on the Scope Variables. If you continue, then you get the error message in the UI, but its too late your not paused any more!
Rather than this code in ScopeChainSideBar.js:
var details = WebInspector.debuggerModel.debuggerPausedDetails();
var exception = details.reason === WebInspector.DebuggerModel.BreakReason.Exception ? details.auxData : 0;
if (exception) {
extraProperties = extraProperties || [];
var exceptionObject = /** @type {RuntimeAgent.RemoteObject} */ (exception);
extraProperties.push(new WebInspector.RemoteObjectProperty("<exception>", WebInspector.RemoteObject.fromPayload(exceptionObject)));
}
a better solution would put the same information in to the red insert for error messages.
The red insert could be removed on resume to let the console put it copy up.
--
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
More information about the webkit-unassigned
mailing list