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

Unfortunately `:default` wouldn't be enough because native checkboxes and radio can also have it. The code could click a native checkbox. MDN's [sample](https://developer.mozilla.org/en-US/docs/Web/CSS/:default) shows this. It comes back authors being able to know the element they are selecting for implicit submission is a button "type" and not just `:default`. Of course, having both `:default` and  `:default-button` could solve this and keep code clean. Though, that doesn't account of submission-blocking form elements (native or FACE).

Or, we ask the browser to perform the steps. I thought of it being on `<form>`. It's just a matter of, do we want that function available anywhere, or scoped to just Custom Elements (which we can do with `ElementInternals`).

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

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