Publishing an attribute named 'disabled' generates exception in IE10

[sorvell]

<polymer-element name="x-test" attributes="disabled">

TypeError: Unable to get property 'disabled' of undefined or null referenceTypeError: Unable to get property 'disabled' of undefined or null reference.

The error occurs when the 'disabled' property's value is looked up on the base prototype, in this case and object derived from Object.create(HTMLElement.prototype).

This error may be influenced by the ShadowDOM polyfill, but note that in IE10, just doing this generates an error.

Object.create(HTMLElement.prototype).disabled 
"Invalid calling object"

This behavior may just need to be documented.

[sorvell]

The core issue is this: #123

[JanMiksovsky]

FWIW, I'm hitting what appears to be this same issue in IE 11 as well (version 11.0.9600.16476).

It looks like there's a pending pull request to at least warn users about this, but I wanted to relate an experience trying to work around this annoying behavior in IE. To get a custom element to work in IE, I tried renaming its "disabled" attribute to "isDisabled" (with a capital "D"). The latter still caused IE to choke. It appears that "isDisabled" is itself a magic property in IE. When I changed my attribute to "isdisabled" (lowercase "D"), IE tolerated it. I mention this in case others try to work around IE's problem with "disabled" with the still-somewhat-legible isDisabled name. That won't work. sigh

[sorvell]

Closed in favor of #123