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 27766 - Clarify whether sessionId is optional from the perspective of the local end before newSession
Summary: Clarify whether sessionId is optional from the perspective of the local end b...
Status: NEW
Alias: None
Product: Browser Test/Tools WG
Classification: Unclassified
Component: WebDriver (show other bugs)
Version: unspecified
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: Browser Testing and Tools WG
QA Contact: Browser Testing and Tools WG
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-01-06 15:30 UTC by Andreas Tolfsen
Modified: 2015-01-06 15:30 UTC (History)
1 user (show)

See Also:

Attachments

Description Andreas Tolfsen 2015-01-06 15:30:26 UTC 
Section 2.1 says that sessionId by default is null, but the WebIDL marks it as optional.

It's called out explicitly on the other parameters to the command object which are to be provided by the local end, but it's unclear if this applies to sessionId.

The question is whether sessionId should be undefined or null when calling newSession.

Since the spec allows a passing in a sessionId to newSession, it follows that local ends shouldn't send null to mean “undefined” since that (in section 4.1.1) talks about whether the field is “set” or not.