Allow JavaScript exceptions to be re-thrown by native bindings

[magreenblatt]

Original report by me.

---

Original issue 317 created by magreenblatt on 2011-08-30T15:43:17.000Z:

Currently, JavaScript exceptions resulting from calling CefV8Value::ExecuteFunction() are returned as a string. It would be nice if these exceptions could be re-thrown for handling by the JavaScript application. For example:

// JS application starts
function jsFoo() { throw "oops"; }
window.registerCallback(jsFoo); // native C++ method

// JS asynchronous operation
try {
window.execCallback(); // native C++ method that executes jsFoo()
} catch (e) {
// got "oops" here
}

[magreenblatt]

Comment 1. originally posted by magreenblatt on 2011-11-10T22:58:01.000Z:

Revision 371 introduces CefV8Exception for returning detailed exception information from CefV8Value::ExecuteFunction*() and adds the ability to re-throw exceptions.

[magreenblatt]

• set state to "resolved"

[magreenblatt]

Original comment by Dmitry Azaraev (Bitbucket: Mystic Artifact).

---

Comment 2. originally posted by fddima on 2011-11-10T23:09:00.000Z:

How it works?
Just preserve initial v8 exception with losing of v8->native / native->v8 transitions?

[magreenblatt]

Comment 3. originally posted by magreenblatt on 2011-11-10T23:36:22.000Z:

If the |rethrow_exception| argument to ExecuteFunction*() is true the original exception will be re-thrown. The values available via CefV8Exception are a copy of the values that existed in the original exception. See:
http://code.google.com/p/chromiumembedded/source/browse/trunk/libcef/v8\_impl.cc?spec=svn372&r=371comment 10.86

The new V8Test.Exception test verifies this behavior.