- From: <bugzilla@jessica.w3.org>
- Date: Mon, 07 Apr 2014 20:54:51 +0000
- To: public-browser-tools-testing@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=25285
Bug ID: 25285
Summary: Boolean attributes return null in both situations - if
browser returns undefined and if browser returns false
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: botalov.andrey@gmail.com
QA Contact: public-browser-tools-testing@w3.org
CC: mike@w3.org
The spec says:
"Because of this, the WebDriver API offers a single command
("getElementAttribute") which covers the case of returning either of the value
of a Document element's property or attribute."
But actually spec defines its own algorithm that isn't similar to neither
returning property nor returning attribute in case if boolean attribute is
supplied.
Consider the following:
<input id="id1" type="checkbox" />
<input id="id2" type="text" />
<span id="id2"></span>
In browsers "checked" will return false for the first and second elements, but
undefined for the third element.
An implementation of Webdriver protocol will return null in all cases.
IMO it's not good. IMO it would be better if Webdriver will return the same
values (true/false/null) as W3C specs say browser to return.
--
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Monday, 7 April 2014 20:54:54 UTC