Include stack trace in error responses

Section 2.4 on the Processing Model doesn't allow us to pass back a stack trace when an error occurs.

This is useful when an executeScript and executeScript throws an error, when the remote end has an internal error and a stack trace is available, or otherwise when a trace is available.

My suggestion is to add to “send an error” the following additional step:

> Let <var>stacktrace</var> be an implementation-defined string containing a stack trace report of the active stack frames at the time when the error occurred.

Ayes, nays?

Received on Monday, 13 April 2015 12:47:53 UTC