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

> No. Although I see a number of arguments are presented to you in detail, so I find your characterisation of "stonewalling" unconvincing.

If you look up a few lines you'll see this:
> OK so we can use the template to get around the restriction - got it. I'm still wondering whether it is a good idea to soup up the template API to do more work vs. allowing dedicated elements to do it?

That's me asking a simple opinionated question.  I have my view, but If I'm wrong it won't be the first time.  

Then that's followed by .... you know what I mean.  And what follows does not attempt to explore that question in any detail.  That's what I mean by stone walling.

> I repeat my request to everyone to stick to a polite and respectful continuation of that discussion if there is more to add.

I think that's a great idea and we will all have a much better time here if we check our opinions at the door and stick to simple examples.

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