- From: <bugzilla@jessica.w3.org>
- Date: Sun, 19 Oct 2014 20:56:23 +0000
- To: public-browser-tools-testing@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=27103
Bug ID: 27103
Summary: Allow nested dictionaries in capabilities
Product: Browser Test/Tools WG
Version: unspecified
Hardware: All
OS: All
Status: NEW
Severity: normal
Priority: P2
Component: WebDriver
Assignee: public-browser-tools-testing@w3.org
Reporter: vlotoshnikov@gmail.com
QA Contact: public-browser-tools-testing@w3.org
CC: mike@w3.org
Blocks: 20860
Section "3.1.2 Methods" specifies for method get():
"Return type: (DOMString or boolean or long), nullable".
https://dvcs.w3.org/hg/webdriver/raw-file/default/webdriver-spec.html#methods
"capabilities" dictionary also is specified to only be allowed DOMString or
boolean or long values, too.
Some existing drivers - to not name names - don't comply with that, e.g.
browserXOptions' value below is not a DOMString or boolean or long:
{
"desiredCapabilities": {
"browserName": "browserX",
"platform": "platformY",
"browserXOptions": {
"browserXSetting": "customValue"
}
}
}
Should the spec change to allow the nested dictionaries (and effectively
arbitrary JSON) in the capabilities? Or do we want to change existing
implementations that aren't currently compliant?
--
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Sunday, 19 October 2014 20:56:25 UTC