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

FWIW, we have no doubt that being able to extend a native builtin element is useful. However, we don’t think the customized builtin as currently spec’ed is the right approach. We have provided more nuanced feedback about various aspect of `is` attribute in the past.

We could have spent another three years debating how to do it properly but we wanted to focus on the minimum viable product that can be shipped on all browsers sooner than that.  This is why we’ve been advocating to move this feature to v2 level, and focus on shipping on the autonomous custom element for now.

Note that there were many other proposals and features, some of which are extremely simple like automatically cloning template contents in `attachShadow` as an optional argument, we wanted to add in v1 Shadow DOM and Custom Elements APIs but we retreated those in the favor of shipping the MVP sooner.

-- 
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-266174073