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

> your demo example does not work without JS

Neither do custom elements.  

> The fact you don't consider all examples already described like template or even html

Why would you want to PE the html tag?  Or more importantly how many developers want to PE the HTML tags and when do they want to do this?

The `is` might be useful in certain cases.  Sort like a nail and a 2X4 could be useful on an oil platform.  The dude's on the platform might be like "Umm....What are you doing with that 2X4?

> That one, I am afraid, I cannot fix.

I know.  And that is what the core argument should be about.  I'm guessing `99.9999%` of developers are going to be looking at exactly this scenario.   So should we add to the developer learning curve with `is` to support `0.00001%` of use cases?

And if it's really easy to handle those cases with what we already now, then why is the `is` even in the spec?


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