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

I have kept myself generally informed of Custom Element progress, but have been out of active development in this area for a couple years (I was a contributor to this spec in the v0 phase). Now that I am revisiting this area of dev to do meaningful work, I'm honestly astonished to see this is still unresolved.

Being able to extend native elements in a way that leverages existing accessibility mechanisms/strategies, while providing a clear declaration syntax in markup, is something this group needs to account for - full stop

The `is` attribute, or any API option for that matter, has its nits and rough edges, but I have seen nothing compelling enough on the anti-is side to dissuade me from the opinion that anti-is-ers are the acting as the perfect-seeking enemies of good.

Do the right thing - get this resolved.

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