28060 2015-02-19 22:53:58 +0000 Should be possible to return errors with executeAsyncScript 2016-09-20 11:30:42 +0000 1 1 1 Unclassified Browser Test/Tools WG WebDriver unspecified PC Linux NEW P2 normal --- 24121 1 jleyba public-browser-tools-testing dburns juangj mike public-browser-tools-testing oldest_to_newest 118043 0 jleyba 2015-02-19 22:53:58 +0000 The callback provided to the executeAsyncScript function only accepts a single argument that is always treated as a successful completion. It should be possible for users to call this function with an error to indicate their script failed. Node.js has popularized the "Error-first" callback approach: errors are passed as the first argument, successful values the second. Another option would be to standardize on the Error-type. If the callback is invoked with an instanceof Error, the script is marked as a failure. 123970 1 jleyba 2015-10-27 17:54:44 +0000 Here's another option: Change executeScript to recognize Promise[1] return values and eliminate executeAsyncScript as a command. If executeScript returns a promise, wait for it to settle. If the promise is resolved, use the resolved value as the command result. If the promise is rejected, return the reason with the command failure. If the promise doesn't resolve before the script timeout expires, fail the command. If there is a page unload event before the promise is resolved, fail the command (covering existing behavior of executeAsyncScript). [1] https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Promise