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

> However, there is an alternative approach. Instead of looking builtin elements as some sort of a magic box which provides a bag of functionalities and capabilities, we can decompose them into a small set of primitive APIs that let each element provide such capabilities. For example, an input element uses the capability to make itself focusable, has a shadow tree with a contenteditable, and participates in a form submission process along with many other things.

@rniwa That is such a cool, outside-of-the-box suggestion. It would be iterative, too, which would hopefully mean that devs could be drip-fed the solutions they're yearning for.

I'm interested in exploring the path this is going down because it feels like, if there is a direction for this, library authors can start providing abstractions similar to how these might be used natively, thus not only giving a stop-gap API that is similar to the WC future, but also being able to provide extensions in a similar manner.



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