25285 2014-04-07 20:54:51 +0000 Boolean attributes return null in both situations - if browser returns undefined and if browser returns false 2016-09-02 20:52:10 +0000 1 1 1 Unclassified Browser Test/Tools WG WebDriver unspecified All All RESOLVED FIXED P2 normal --- 20860 1 botalov.andrey simon.m.stewart dburns mike public-browser-tools-testing oldest_to_newest 103502 0 botalov.andrey 2014-04-07 20:54:51 +0000 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. 127285 1 simon.m.stewart 2016-09-02 20:52:10 +0000 getAttribute, as discussed in this bug, was removed from the spec. Closing.