Re: [WICG/webcomponents] Form-associated custom elements: being a submit button (#814)

EisenbergEffect left a comment (WICG/webcomponents#814)

@bahrus You are reading too much into my example. It's not intended to be an actual proposal. It was just a quick sketch of an idea based on what some native platforms do.

My point is that we should have a more general way to mix behavior into elements (or enhance if you prefer that language), so we don't persist in these one-off solutions for every special behavior that comes up. 

If folks agree on your proposal, great. I don't see why it couldn't handle this scenario just fine. This kind of pattern has been successfully used for at least 20 years on plenty of other platforms (WPF, Unity3d, UiKit, SwiftUI, Jetpack Compose, Unreal Engine, etc.) for both 1st and 3rd party behaviors/enhancement. The key is to not think in terms of 1st and 3rd party at all, but instead to think of unifying platform primitives.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/WICG/webcomponents/issues/814#issuecomment-3392840225
You are receiving this because you are subscribed to this thread.

Message ID: <WICG/webcomponents/issues/814/3392840225@github.com>