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

> Once you'll show me a table that works same as the following one avoiding is attribute, I'll start replying because right now all I think is that you are trolling.

Right - pointing out that your `x-map` demo is not even a candidate for `is` PE is just trolling.

``` html
<table is="sor-table">
  <tr is="rainbow-row">
    <td is="special-td">how to tr and td without is attribute?</td>
  </tr>
</table>
```

I'll give you this one.  How are users going to feel when the `row` is not a `rainbow-row` and the `td` is not special, and the whole table is not sortable?  You can do this, but how often is a user going to be in a situation where this is not just a sparrows fart in the middle of Alaska?

> Once you'll show me a <template is="special-template"></template> that works like a template would, you'll probably have other developers attentions too.

I'm pretty sure I have their attention.  What does `special-template` do?  It's inert to start with, so users don't know it exists, and once you have javascript anything you can provide utility functions that will do anything you can do within `special-template`.





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