28780 2015-06-08 14:37:18 +0000 3.7 Handling Errors - Should first JSON field be called "status" and not "error"? 2015-06-09 13:39:56 +0000 1 1 1 Unclassified Browser Test/Tools WG WebDriver unspecified PC Windows NT RESOLVED FIXED P2 minor --- 20860 1 paulgrime public-browser-tools-testing ato dburns mike public-browser-tools-testing oldest_to_newest 120826 0 paulgrime 2015-06-08 14:37:18 +0000 The following sentence uses "error" twice for JSON field names. Is this correct? Should one be "status"? "This JSON body has two fields: error, containing a string indicating the error type and error containing an implementation-defined string containing a human readable description of the kind of error that occured." 120827 1 paulgrime 2015-06-08 14:38:24 +0000 https://w3c.github.io/webdriver/webdriver-spec.html 120828 2 ato 2015-06-08 15:01:17 +0000 Thanks for noticing this. The body sent back as part of an error response should have three fields, of which two are implementation-defined (meaning they can be empty strings): { "error": "no such element", "message": "Could not locate element by locator: …", "stacktrace": "" } I’ve opened https://github.com/w3c/webdriver/pull/87 to reflect this. There are more commands that haven’t yet been changed to use the new dispatch architecture that still use the term “status”, but we can fix these as we redefine them. 120838 3 dburns 2015-06-09 13:39:56 +0000 landed in https://github.com/w3c/webdriver/commit/1f55f3ec285daf2665f28305c1e24595a4eb040e