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

Angular 4 is gaining a lot of momentum and the reality is that we are going to have a lot of sites using it.  Lets assume it gets 1/10 of the application market.  It would be insane to have millions of sites with custom elements that are simply not accessible for screen readers, etc.  So the W3C needs to be concerned with how custom elements can be made accessible within the the applications that will be delivered by frameworks like angular 4 etc.  Angular 4 has 0 (AFAIK) mention of the 'is' attribute, so there has to be a better solution. 

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