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

I am saying we should not drop the v0 `extends` behavior which has been adopted for valid reasons and used in production already.

I've often read some spec is driven by libraries and adoption, `v0` is a clear example we should not ignore. V1 is more ES6 friendly, but less real-world useful if it won't have `is` in it, like it is already accordingly with current specifications that have been already polyfilled and adopted.

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