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

I'm only addressing the example demo you've displayed, because that's something we can all see the code for.  I've also said that we can do this with a `<inline-write>` element.  So my question is why do it differently, because I believe in the premise that the `is` syntax really is confusing or not that it's confusing but it's less clear and will lead to solutions that are really hacks built on top of a hack.

The other examples I can't comment on because there's no nor markup displayed.  If you say with `<script is="x-sharder" type="x-shader/x-fragment">` contained within this context the end result is _________________, then I can actually comment on it.

BTW I think we are both having a pretty good discussion here.

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