Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509)

Since Chrome 67 shipped Custom Elements with Builtins extend capability, and since Firefox is planning to release those as well, I have updated my polyfill and its [test page](http://webreflection.github.io/document-register-element/test/) to welcome native implementations to test against that page.

If your implementation passes all tests, the `window.customElements` object will be the native one, instead of the patched one.

This is already true for Chrome 67, I hope it'll be true for Firefox too once shipped.

### Fun fact
The `ce.getAttribute('is')` returns always `null` even if `ce.outerHTML` would expose the `is="custom-element"` information. Not sure that was a bug, but it's easy to mess up with feature detection if you don't know that.

Thanks to the Chrome team for going out in a pragmatic way fulfilling the Custom Elements specification as a whole 🎉 

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/webcomponents/issues/509#issuecomment-393522912