I'm always for the least "_overthinking_" when it comes to names.
If @rniwa says "_that's pretty much mixins_" and the word _mixins_ came up already to describe this intent (and nobody asked "_what do you mean by mixins_" ) maybe _mixins_ is the term to use?
```html
<any-element mixins="behavior1 behavior2" />
```
That would work, it would put an end to the `is` confusion and story, it can be easily polyfilled too.
--
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-327722495