in polymer 0.0.20131025 element id attribute not allowed

[jeroldangarcia]

"id" attribute declaration in a polymer-element now causes an error:

example:
polymer-element name="w5-empty" attributes="id"

error:
TypeError {stack: "TypeError: Cannot read property 'id' of undefined↵…/www.polymer-project.org/polymer.min.js:35:25304)"}
"TypeError: Cannot read property 'id' of undefined
at c.Object.defineProperty.get as id
at c.publishAttributes (http://www.polymer-project.org/polymer.min.js:37:6716)
at f.buildPrototype (http://www.polymer-project.org/polymer.min.js:37:7569)
at f.register (http://www.polymer-project.org/polymer.min.js:37:7341)
at h._register (http://www.polymer-project.org/polymer.min.js:37:9870)
at h.registerWhenReady (http://www.polymer-project.org/polymer.min.js:37:9827)
at h.createdCallback (http://www.polymer-project.org/polymer.min.js:37:9599)
at j (http://www.polymer-project.org/polymer.min.js:35:24719)
at g (http://www.polymer-project.org/polymer.min.js:35:24327)
at Object.p as upgrade"

[jeroldangarcia]

The same for "title"

[jeroldangarcia]

I think they do this on porpouse in order to avoid conflicts between the
custom-element attributes and global tag parameters...

On 05/12/13 02:39, Po-Ying Chen wrote:

I have same problem too.

—
Reply to this email directly or view it on GitHub
#332 (comment).

[dfreedm]

Sorry for letting this issue fall through the cracks.

In general, it's a bad idea to attempt to redefine native DOM attributes like "id".
The reason for this failure is related to how DOM properties are defined, which is very complicated.
Suffice it to say that "id" and properties like it are somewhat magical.

It would probably be beneficial to warn when you accidentally touch one of these properties so at least the error makes sense.

[dfreedm]

I'll close this in favor of #379, which will add warnings for situations like this.