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

PE is the only compelling argument. From a development perspective, `is=""` not so appealing, but for PE it is.

However, in my personal cases, if you don't have JavaScript, I don't care. I'm targeting those people that have modern technologies enabled (and by correlation, those people probably have money to buy/use my products).

If something like `<my-button extends="button" />` can be specc'd so that a browser knows to fallback to `<button>`, then even a text-based browser like elinks can update to follow the spec and it will work there.

If we follow the current `<button is="my-button">` in the current order, then there's also the question of what something like `<my-better-button is="my-button">` does, and how can that ever fall back to `<button>`?

Maybe there can be a new non-javascript way of specifying fallbacks for those who really want it, maybe in CSS or some other file (JSON file)?

```css
my-button extends button;
```

```json
{
 'extensions': {
  'my-button': 'button'
 }
}
```

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