[Webkit-unassigned] [Bug 128776] New: Web Inspector: JSContext inspection should report exceptions in the console

[bugzilla-daemon at webkit.org]

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

           Summary: Web Inspector: JSContext inspection should report
                    exceptions in the console
           Product: WebKit
           Version: 528+ (Nightly build)
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: Web Inspector
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: joepeck at webkit.org
                CC: timothy at apple.com, ggaren at apple.com,
                    joepeck at webkit.org,
                    webkit-bug-importer at group.apple.com,
                    mark.lam at apple.com, graouts at apple.com


When debugging a JSContext it would be important to report errors and exceptions to the inspector.

When interacting with a JSContext/JSContextRef such exceptions can be triggered through any API call. For example (C APIs mentioned below because the ObjC APIs just funny through to the C APIs):

    • parse errors:
        - JSEvaluateScript given an invalid program
    • runtime errors:
        - JSEvaluteScript that causes a runtime exception (e.g. JSEvaluteScript("{}.a"))
        - API calls that trigger a runtime exception (e.g. JSObjectCallAsFunction(...) calling a function producing an exception).

At the same time, it is also important that we stash at least a basic amount of information about JSContext exceptions even when an inspector is not attached. That way, if there was an exception, when the user eventually opens Web Inspector we can already tell them about the exceptions that happened in their Context.

This is an important debugging scenario, equivalent to opening Inspector on a Web Page that has had exceptions before Web Inspector was opened.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.