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

noamr left a comment (WICG/webcomponents#814)

I think that based on the feedback here and prior art from other platforms, the proposal went towards something that "feels" very modular (an array of behaviors). I understand the sentiment behind that.

However, the benefit of this and how it would work in practice remains somewhat vague, with a lot of the conflict resolution semantics making the modularity into something of a false promise or something of hypothetical future value.

I've created a counter proposal [here](https://github.com/MicrosoftEdge/MSEdgeExplainers/issues/1353) that specifically doesn't introduce any new generic form of composition, but rather just fixes "activation behavior" - how do we take the lowest possible bundle of behaviors that express "activation" (submit-button, regular button, link, etc) and use those to make an element into "a submit button" or one of the other things.

This would be exclusive though - there would be no API way (atm) to express "this is a button link" or "this is both a submit and a reset button". This kind of scenario would be un-expressible in the API rather than a new set of error scenarios.

Note that "activation behavior" *can* be composed with future behaviors - the same way it can be composed with other element internals. But it doesn't come with a generic form of API but rather a specific thing that addresses this problem.


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

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