Bug 48598
| Summary: | WebScriptDebuggerDelegate: Cannot Tell if an Exception is Uncaught | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Joseph Pecoraro <joepeck> |
| Component: | WebKit API | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | Normal | CC: | joepeck, kelly_robinson+webkit |
| Priority: | P2 | ||
| Version: | 528+ (Nightly build) | ||
| Hardware: | PC | ||
| OS: | OS X 10.5 | ||
Joseph Pecoraro
The "hasHandler" information for exceptions is lost when notifying the WebScriptDebuggerDelegate.
It may be useful for the delegate to know if the exception was uncaught or not.
The information is available, before calling the delegate, but it is ignored (note "hasHandler"):
http://trac.webkit.org/browser/trunk/WebKit/mac/WebView/WebScriptDebugger.mm#L203
Inspector uses that information to identify an "uncaught" exception:
http://trac.webkit.org/browser/trunk/WebCore/bindings/js/ScriptDebugServer.cpp#L515
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Joseph Pecoraro
Looks like this is being handled in:
<http://webkit.org/b/52104> Would like script debugging protocol method to differentiate between caught and uncaught exceptions
*** This bug has been marked as a duplicate of bug 52104 ***