Note: these tests were run in Chrome 29.0.1529.3 canary with experimental webkit features turned on.
document.webkitRegister does not work as expected on template content when template.createInstance is used to generate nodes. See the example here and view the dev tools console output:
The issue appears to be that if you touch the node before it's put into the right document, it isn't upgraded (try commenting out the instance.firstChild; line
Note: these tests were run in Chrome 29.0.1529.3 canary with experimental webkit features turned on.
document.webkitRegister does not work as expected on template content when template.createInstance is used to generate nodes. See the example here and view the dev tools console output:
http://jsbin.com/uqeqen/1/edit
However, when cloneNode is used to generate nodes, the elements do upgrade. See:
http://jsbin.com/uqeqen/2/edit
Based on this Custom Elements spec bug, this behavior is somewhat surprising.
That createInstance fails where cloneNode does not suggests that there is a bug in the implementation of createInstance.