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

I think it's premature to try to come up with a set of compassable features like that. I think we need to first come up with a list of use cases that aren't adequately addressed by the current Web API (besides `is` attribute), and spec API for those.

Once we have those privatives to solve those problems, I can see bundling some of them up to make it easily compassable seems like a sensible approach but perhaps this is an area we can leave to library/framework authors first. Once it became obvious that every library/framework is having some basic set of feature as a composable function/class, etc... then we can standardize them.

In general, adding new features to browsers is slower & more painful process so we should be adding things that are already well vetted in JS library/framework.

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