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

I love the idea of breaking all native "specialness" out into element-traits so to speak. Personally I'd like to see this go in this order:
1. Create an exhaustive list of "magic native traits" that exist on built-in elements today.
2. Add a way to buy into buckets of these traits based on existing elements when defining a custom element. (effectively this would meet most of the needs of this discussion)
3. Break said traits out into fully separated bits that can be mix/matched/composed

It is worth noting however that this approach will have one major drawback in the end. Since we don't have proper interfaces in javascript it won't be easy to select elements in css or via dom api's that are effectively input boxes. Perhaps a pseudo for these traits would be in order?

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