This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 28781 - Section 9.1.2 findElement() should include the sessionID and response code in the response object
Summary: Section 9.1.2 findElement() should include the sessionID and response code in...
Status: RESOLVED FIXED
Alias: None
Product: Browser Test/Tools WG
Classification: Unclassified
Component: WebDriver (show other bugs)
Version: unspecified
Hardware: PC Windows NT
: P2 normal
Target Milestone: ---
Assignee: Browser Testing and Tools WG
QA Contact: Browser Testing and Tools WG
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 20860
  Show dependency treegraph
 
Reported: 2015-06-09 15:48 UTC by John Jansen
Modified: 2016-05-09 10:04 UTC (History)
3 users (show)

See Also:


Attachments

Description John Jansen 2015-06-09 15:48:47 UTC
Let result be equal to {"element-6066-11e4-a52e-4f735466cecf": id}"

I remember discussing this one[1], but for some reason I was expecting that in addition to our 'guid' generation, we would also want to get back the sessionId and response code. If that is being intentionally left off the object, can you explain why?

[1] http://www.w3.org/2014/10/30-testing-minutes.html
Comment 1 James Graham 2015-06-09 16:00:19 UTC
For successful responses there isn't a response code; so you only get that for errors. The session id is superfluous since the client had to send it in the request anyway it presumably already knows what it is.
Comment 2 David Burns :automatedtester 2016-05-09 10:04:27 UTC
I believe this has been fixed with the find element rewrites