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

@trusktr wrote
> If we keep it on merit of understandable syntax, then why not keep it in the same direction as JavaScript?

That's not the primary reason for it. The primary reason is the HTML parser - which gives special magic to elements having their native HTML name.

I agree with others that the syntax is kind of ugly, but it solves a specific concrete problem. The extends stuff would be nice - not least because you could make it do mix-in things to extend both tr and input type="date" in a single custom element. But that seems more like a nice new thing than solving an existing problem.

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