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

@rniwa 

> We could have spent another three years debating ...

FWIW, the reason most of us are here defending `is=""` is that nobody wants to wait other 3 years before being able to extend native builtins, specially when `is=""` solution,as ugly as it is, already worked for the last 2 years and keeps working without problems polyfilled.

Any possible improvement for V2 would be welcomed by everyone, but how about we move the Web forward **today** ?




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