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

> > I think it's best if we try and get this discussion back on track.
> Agreed. However, we already wrote ideas but @rniwa says he needs more use cases or libraries implementing something impossible to implement without is="" so we're fully stuck in a circle here.

Why do you think it's impossible to implement? My proposal is to find use cases which can't be satisfied without `is`, e.g. setting default accessibility role, and fix those problems by adding new API. Once we've done that, library/framework can use mixins, pure functions, etc... to make it developer friendly as they wish. If one or another approach proves to be superior to others and all libraries / frameworks end up duplicating the work, we can just standardize it. It is pretty clear to me at this point that many people have different opinions on how to approach this, and it's probably best to let Web developers experiment it first (in terms of how to make it developer friendly, not to add those APIs).

My take on future directions of Web components is to chip away many small pieces. e.g. form submission participation, default ARIA roles for custom elements, etc... Some of those incremental improvements can be polyfiable but others may not be if we're exposing a fundamentally new capability to the Web. But that's okay.

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