On Fri, Feb 6, 2015 at 2:13 AM, Chris Bateman <chrisb...@gmail.com> wrote: > ** Bonus issue - I didn't know this, but Chrome doesn't upgrade when you add > the is= attribute to an element that's already been created. Ember builds up > its templates into document fragments - so the input failed to upgrade in > Chrome. This doesn't happen with the polyfill, however, so I got around the > issue by forcing the polyfill to override the native > document.registerElement.
Note that this isn't an issue in the sense of "Chrome gets it wrong" - the spec mandates this behavior. The is='' attribute is similar to the tag-name, in that it determines the identity of the element, and thus must be around at creation time. ~TJ
