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

Hi guys, just wanted to add this.
My teem is using custom elements (v0) for 2 years now, we launched about 20 big and expencive corporate websites. Most of them are heavily dependant on custom elements. About 50% of custom elements are extensions of build-in native elements (using is=""). This is a really good sintax that lets us easily see what element is what in html. 
It really hurts that we cannot move to v1 because one major browser is violating custom elements specs and does not support "is" attribute.

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