Re: [w3c/webcomponents] accessibility considerations: states and behaviors (#567)

P.S. I'd like to underline that not only my polyfill always followed specs and implemented `extends` but even `webcomponents.js` and `Polymer` has used this feature:
https://github.com/webcomponents/webcomponentsjs/blob/v1-polymer-edits/src/CustomElements/v1/CustomElements.js#L577-L581
I'm not sure what kind of extra evidence we need to put an end to this dispute about `is`: it's already shipped, with out 100% consensus.

Developers used and needed it. I don't have more to add to this discussion so I'll stop here. I hope my points are clear (or at least my point of view).

-- 
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/567#issuecomment-247119618