[Bug 27733] New: [WebDriver Spec]: attr.specified shouldn't be checked by getElementAttribute

https://www.w3.org/Bugs/Public/show_bug.cgi?id=27733

            Bug ID: 27733
           Summary: [WebDriver Spec]: attr.specified shouldn't be checked
                    by getElementAttribute
           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
            Blocks: 20860

According to the [DOM spec](https://dom.spec.whatwg.org/#attr) attr.specified
always returns `true`.

Therefore I think it's not necessary to use `getAttributeNode`:

> If result is null or undefined, or if it is an object, set the value of result to be the value of the AttributeNode obtained by calling getAttributeNode on element iff that AttributeNode is specified. That is, result is the equivalent of executing the following Ecmascript: var attr = element.getAttribute(name); var result = (attr && attr.specified) ? attr.value : null;

change into:

> If result is null or undefined, or if it is an object, set the value of result
 to be the value obtained by calling getAttribute(name) on element.

Also `name` may be in e.g. upper case at that step of the algorithm. I think it
would be better to convert it to lower case at the first step of the algorithm
and don't say that it should "match insensitively"

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Saturday, 3 January 2015 13:00:27 UTC