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

@WebReflection The main difference with my suggestion is that rather than saying that some native element IS another element it would be a way of adding native interfaces to existing elements. My example was confusing:
```html
<my-button is="button-like"></my-button>
```
And for the css case I intentionally used a pseudo because the goal is not to select elements that JUST contain an attribute (also while not stated I imagined that this attribute would take multiple values e.g. `<foo-bar implements="input-like" />`. So the goal is to select elements that implement the interface which may have been defined at registration time in script or have been an existing interface on current built-ins.

```css
:implements(input-like) {}
```
The above would select any existing form input elements plus anything that has the interface regardless of whether it was added in markup or at definition time.

>From a naming perspective I understand there would be conflict potential to use `is=""` and `is:()` but they would be MY PERSONAL ideal.

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