attached being called twice with canary

[duralog]

hey guys, I love x-tags - and started using it extensively - yet no matter what I do on chrome canary, the attached callback will get called twice.

the first time, it's called when calling appendChild. the second time comes from the observer callback. if you request, I can give a screenshot - yet I think it's easy enough to reproduce.

I'm on OSX: 40.0.2195.0 canary (64-bit) ... firefox doesn't have the problem, lol

[csuwildcat]

Can you just create a simple test using jsBin or jsFiddle? I can take a look this evening.

[duralog]

wow, that was an experience... I think I hijacked some dude's fiddle too...

see if this works for you. http://jsfiddle.net/n39wb/16/

you should see:

element goes here
created: attached! attached!

[duralog]

if it helps, I commented out the line, CustomElements.parser.parse(document); in the bootstrap function to continue working...

thanks a whole lot dude!

[csuwildcat]

Is that line in X-Tag Core, or the Web Components polyfill we share with Polymer?

[csuwildcat]

So I just looked, and it's happening on Chrome 38 mobile, the release version. The line at issue isn't in X-Tag Core, it's from the polyfill. At first blush, this looks like the polyfill not recognizing the native Web Components implementation correctly, resulting in a double call of the lifecycle callback. Can you also file this on the polyfill repo Google maintains? I can follow up with those guys to get it resolved.

[csuwildcat]

Here's the repo issue section for reference: https://github.com/Polymer/webcomponentsjs-dev/issues

[csuwildcat]

@pennyfx can we see if sucking in the latest from their polyfills fixes this?

[csuwildcat]

This no longer occurs after various updates to the polyfills. If it reoccurs, please reopen.