[Bug 28060] New: Should be possible to return errors with executeAsyncScript

https://www.w3.org/Bugs/Public/show_bug.cgi?id=28060

            Bug ID: 28060
           Summary: Should be possible to return errors with
                    executeAsyncScript
           Product: Browser Test/Tools WG
           Version: unspecified
          Hardware: PC
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: WebDriver
          Assignee: public-browser-tools-testing@w3.org
          Reporter: jleyba@google.com
        QA Contact: public-browser-tools-testing@w3.org
                CC: mike@w3.org

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.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Thursday, 19 February 2015 22:54:00 UTC