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

@oleersoy as you have asked for demos, code and use cases - here you have real code, demos and examples for just one of many use cases for `is`   https://github.com/Juicy/imported-template (plus https://github.com/Juicy/juicy-html)

Here you have an article with rationale, why I find such element useful  http://starcounter.io/html-partialsincludes-webcomponents-way/

This single custom element is being used for 3 years now, for somewhat around 2 yrs it's used on production by many companies. 

> No they don't and that's why you can't produce a single case where they actually do.

I know in person at least 20 developers from 4 different companies who uses that element. That's why, please don't say so.

As it was mentioned many times above, such use case is not achievable without `is` (or something conceptually similar). `<imported-template>blah</imported-template>` would be simply rendered as a block element, and that is something we should avoid.

If anybody knows better alternative to implement that, I'd would be more than happy to hear it.




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