isEnabled() assertion returns incorrect value for disabled <label> element

I just discovered what I am pretty sure is a bug.

The markup I am using looks like this:

<label id='blah-label-id' disabled="disabled" data-ng-click="handleClick()">
<input type="radio">blah</label>

The Protractor assertion I am using looks like this:

expect(element(by.id('blah-label-id')).isEnabled()).toBe(false);

However, the above assertion fails.

When I test it to see the result of isEnabled(), it returns true, when you’d expect it to return false.

I have tested this by calling getAttribute('disabled') on the same element – it returns 'true' (as a string, not a boolean value).

Note that in the same suite of tests, I am successfully using the isEnabled() assertion on <input type="range">, <input type="text"> and <button> elements.

[mcalthrop]

I’m using Chrome 33.0.1750.117 on OSX 10.9.2.

It’s a bit of a nuisance, because I spent a lot of time thinking that the test had failed.

But I have the workaround of using this:

expect(element(by.id('blah-label-id')).getAttribute('disabled')).toBe('true')

[awerlang]

Certainly this behavior is not convenient, but I think it is a correct implementation of HTML 5 specs.

See, a and span doesn’t have a disabled attribute.

• https://developer.mozilla.org/en-US/docs/Web/HTML/Element/span
• https://developer.mozilla.org/en-US/docs/Web/HTML/Element/a
• https://developer.mozilla.org/en-US/docs/Web/HTML/Element/label
• https://developer.mozilla.org/en-US/docs/Web/HTML/Global_attributes

If getAttribute() works, it must be because the way angular implements directives.

As a personal note, these abstractions brought to us by frameworks like bootstrap may hide such subtleties, but we must be aware of.