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

> pointing out that your x-map demo is not even a candidate for is PE

the `is` attribute has been around for years now in V0. I have said it's an old demo but feel free to keep talking about it.


> I'll give you this one.

There are other similar cases, specially with nested elements with meanings such `LI` or `DT` or `PICTURE` or others. You'd give me all of them because like I've said already in my first reply to you:

> **There are no valid and universally compatible alternatives** to this approach, so it's a matter of when rather than if these are needed.


Moreover ...

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

They'll have a table with tabular data. This is the graceful enhancement everyone talked about so far in here.


> You can do this, but how often is a user going to be in a situation where ...

Every user with a browser that hasn't fully adopted the **current specifications**, since you said polyfills are not an option for you.

In my case? Nobody, the polyfill has hybrid mode support so that your flavor of `<custom-elements>` work natively, and those with builtins `is` and `extend` work polyfilled.

This is how custom elements worked for the last 2 years, via polyfills, ask AMP HTML team, Skate, Polymer or others how this did go so far, I think _pretty well_ would be the most common answer.

Best Regards



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