Handle JS exceptions in javascript-evaluation-complete.

[aartaka]

The code example in the documentation for webkit_web_view_run_javascript_finish () has a useful idiom in it:

exception = jsc_context_get_exception (jsc_value_get_context (value));
if (exception)
    g_warning ("Error running javascript: %s", jsc_exception_get_message (exception));
else
    g_print ("Script result: %s\n", str_value);
g_free (str_value);

Exposing JS error messages can be useful in debugging bigger things, so we should probably use jsc_context_get_exception in javascript-evaluation-complete callback. To do so:

• Bind jsc_context_get_exception.
• Bind jsc_exception_get_message.
• Bind jsc_value_get_context.
• (optional) Bind other useful methods of JSCException for better error reporting.
• Maybe get rid of (webkit-javascript-result-get-global-context js-result) in javascript-evaluation-complete.

How does that sound?

EDIT: Unmatched parentheses O_o

[Ambrevar]

It sounds very good, my friend :) Thanks for investigating this!

[Ambrevar]

@aartaka Does this work now?

If so, maybe we should add a test.

[aartaka]

I'm not sure it does. Any mangled/semantically wrong/out-of-context JS errors with GErrors instead of the context-based exceptions. No idea, why.