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

I do question if FACE with `submitButton === true` should have that activation behavior done so by the browser (just because it's flagged). I think custom element author should do it.

As of now, we expect authors to call `setFormValue()`. I was expecting that type of opt-in interaction. In other words:

````html
<x-button type=submit onclick="this._elementInternals.form?.requestSubmit(this)">FACE Button</x-button>

<x-input onkeydown="event.key === 'Enter' ? this._elementInternals.implicitSubmit() : null">FACE Input</x-input>
````

As of now, `[disabled]` FACE elements don't fire click events.

Customized built-in elements (`[is]` attribute) don't need to use this. That should be handled by the browser because they're native `HTMLButtonElement` or native `HTMLInputElement` with `[type=submit]` set.


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

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