- From: James Graham <james@hoppipolla.co.uk>
- Date: Mon, 10 Nov 2014 21:26:15 +0000
- To: Jason Leyba <jleyba@google.com>, public-browser-tools-testing@w3.org
On 10/11/14 18:38, Jason Leyba wrote:
> Oops, hit send.
>
> GET /session/{sessionId}/element/{__ELEMENT}/attribute/{name}
> 200 if command finished; response has {"value": X} (X may be null)
> 404 if {sessionId} or {ELEMENT} not valid references
>
> POST /session/{sessionId}/element/{______ELEMENT}/attribute/{name}
> 405: valid command URL, but invalid method
>
> POST /session/{sessionId}/element/
> 200 {"status": "success", "value": {ELEMENT}}
> 200 {"status": "no such element", "value": error-details}
> 404: {sessionId} not found
I think there was some agreement to remove status: from the response
body and use the code to communicate success vs failure. For non-success
responses the body would look like {"error": "reason for error"}
Received on Monday, 10 November 2014 21:26:39 UTC