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

@oleersoy 

> Do you maybe have a few scripted comments for me that you would like me to add?

I don't know what you mean by this.

> Just get rid of stuff like <button is="FancyButton"> because that does not add any value. Being able to extend button and use a <fancy-button> does.

You're entitle to the opinion that using `is` with a button is not useful, but `is=` is still the only way to create a subclass of `HTMLTemplateElement` that works when it's added to the DOM before the subclass definition is loaded. This was pointed out by @tomalec a while ago and is also true for other element types.

Right now, inheritance without `is=` is **impossible**. If you can provide a better alternative that enables creating subclasses of all builtin elements, you will have solved the problem. Since you've made it clear that you don't like `is=`, I think it would be good to move forward now, possibly by suggesting an alternative.

> OK - Everyone take a 10 minute timeout. No Ipad!

Flippant remarks like this are not helpful. 

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