@fusion.dev/helix 0.182.1 → 0.182.2

package/types/jsx.d.ts

@@ -44878,7 +44878,9 @@ export type CustomElements = {
    * submitted nothing and sent no `helix-press`. The control's own click reaches
    * the host's listeners once, retargeted, as one from a native button does. A
    * disabled button does nothing, and a pending one refuses the press.
-   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the button's form changes.
+   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the button's form changes. Its own rather than
+   * an override: the base a button extends watches no form's checks, because
+   * a button reports no verdict of its own.
    * - `formDisabledCallback(disabled: boolean) => void`: Called by the browser when an ancestor fieldset is disabled or enabled.
    *
    * **The argument is the effective state, and taking it whole is what latched
@@ -46413,6 +46415,10 @@ export type CustomElements = {
    * forgetting of a reader's past attempt, whose message otherwise showed over
    * the emptied control the moment the form was reset.
    * - `formStateRestoreCallback(state: string | File | FormData | null) => void`: Brings back the draft when the browser restores the form.
+   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
+   * not. The control shows no message for it: `reportValidity()` does that.
+   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
+   * form's `checkValidity()`, as connecting does for the form it starts in.
    * - `formDisabledCallback(disabled: boolean) => void`: Called by the browser when an ancestor fieldset is disabled or enabled.
    *
    * **The argument is the effective state, and taking it whole is what latched
@@ -46446,15 +46452,11 @@ export type CustomElements = {
    * the fieldset's hold is not recorded. There is no callback to learn it from
    * and reading `:disabled` here would answer about the attribute we are in the
    * middle of removing.
-   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
-   * not. The control shows no message for it: `reportValidity()` does that.
    * - `reportValidity() => boolean`: Returns whether the control is valid, and when it is not, fires `invalid`
    * and shows the browser's message at the control.
    * - `setCustomValidity(message: string) => void`: Marks the control invalid with `message`, or clears that with an empty
    * string, as on a native control. The form does not submit while it is set.
    * - `focus(options?: FocusOptions) => void`: Moves focus to the control, as focusing a native control does.
-   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
-   * form's `checkValidity()`, as connecting does for the form it starts in.
    *
    * ## CSS Custom Properties
    *
@@ -46978,6 +46980,10 @@ export type CustomElements = {
    *
    * Through the base's prototype rather than `super`, because the base this
    * grafts onto is any element and only a form element has the hook.
+   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
+   * not. The control shows no message for it: `reportValidity()` does that.
+   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
+   * form's `checkValidity()`, as connecting does for the form it starts in.
    * - `formDisabledCallback(disabled: boolean) => void`: Called by the browser when an ancestor fieldset is disabled or enabled.
    *
    * **The argument is the effective state, and taking it whole is what latched
@@ -47011,15 +47017,11 @@ export type CustomElements = {
    * the fieldset's hold is not recorded. There is no callback to learn it from
    * and reading `:disabled` here would answer about the attribute we are in the
    * middle of removing.
-   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
-   * not. The control shows no message for it: `reportValidity()` does that.
    * - `reportValidity() => boolean`: Returns whether the control is valid, and when it is not, fires `invalid`
    * and shows the browser's message at the control.
    * - `setCustomValidity(message: string) => void`: Marks the control invalid with `message`, or clears that with an empty
    * string, as on a native control. The form does not submit while it is set.
    * - `focus(options?: FocusOptions) => void`: Moves focus to the control, as focusing a native control does.
-   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
-   * form's `checkValidity()`, as connecting does for the form it starts in.
    *
    * ## CSS Custom Properties
    *
@@ -47264,6 +47266,10 @@ export type CustomElements = {
    * - `click() => void`: Ticks or clears the box, as `click()` does a native checkbox: passed to the control
    * inside, so the one click a listener hears is the control's, after it has
    * moved. See `HostClickController`.
+   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
+   * not. The control shows no message for it: `reportValidity()` does that.
+   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
+   * form's `checkValidity()`, as connecting does for the form it starts in.
    * - `formDisabledCallback(disabled: boolean) => void`: Called by the browser when an ancestor fieldset is disabled or enabled.
    *
    * **The argument is the effective state, and taking it whole is what latched
@@ -47297,15 +47303,11 @@ export type CustomElements = {
    * the fieldset's hold is not recorded. There is no callback to learn it from
    * and reading `:disabled` here would answer about the attribute we are in the
    * middle of removing.
-   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
-   * not. The control shows no message for it: `reportValidity()` does that.
    * - `reportValidity() => boolean`: Returns whether the control is valid, and when it is not, fires `invalid`
    * and shows the browser's message at the control.
    * - `setCustomValidity(message: string) => void`: Marks the control invalid with `message`, or clears that with an empty
    * string, as on a native control. The form does not submit while it is set.
    * - `focus(options?: FocusOptions) => void`: Moves focus to the control, as focusing a native control does.
-   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
-   * form's `checkValidity()`, as connecting does for the form it starts in.
    *
    * ## CSS Custom Properties
    *
@@ -47917,6 +47919,10 @@ export type CustomElements = {
    * Falling back to what the markup declared rather than to empty, because
    * a restore with no state is a form the browser has nothing recorded for,
    * which is the same situation as a fresh one.
+   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
+   * not. The control shows no message for it: `reportValidity()` does that.
+   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
+   * form's `checkValidity()`, as connecting does for the form it starts in.
    * - `formDisabledCallback(disabled: boolean) => void`: Called by the browser when an ancestor fieldset is disabled or enabled.
    *
    * **The argument is the effective state, and taking it whole is what latched
@@ -47950,14 +47956,10 @@ export type CustomElements = {
    * the fieldset's hold is not recorded. There is no callback to learn it from
    * and reading `:disabled` here would answer about the attribute we are in the
    * middle of removing.
-   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
-   * not. The control shows no message for it: `reportValidity()` does that.
    * - `reportValidity() => boolean`: Returns whether the control is valid, and when it is not, fires `invalid`
    * and shows the browser's message at the control.
    * - `setCustomValidity(message: string) => void`: Marks the control invalid with `message`, or clears that with an empty
    * string, as on a native control. The form does not submit while it is set.
-   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
-   * form's `checkValidity()`, as connecting does for the form it starts in.
    *
    * ## CSS Custom Properties
    *
@@ -48329,6 +48331,10 @@ export type CustomElements = {
    * a restore with no state is a form the browser has nothing recorded for,
    * which is the same situation as a fresh one.
    * - `focus(options?: FocusOptions) => void`: Moves focus to the control, as focusing a native control does.
+   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
+   * not. The control shows no message for it: `reportValidity()` does that.
+   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
+   * form's `checkValidity()`, as connecting does for the form it starts in.
    * - `formDisabledCallback(disabled: boolean) => void`: Called by the browser when an ancestor fieldset is disabled or enabled.
    *
    * **The argument is the effective state, and taking it whole is what latched
@@ -48362,14 +48368,10 @@ export type CustomElements = {
    * the fieldset's hold is not recorded. There is no callback to learn it from
    * and reading `:disabled` here would answer about the attribute we are in the
    * middle of removing.
-   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
-   * not. The control shows no message for it: `reportValidity()` does that.
    * - `reportValidity() => boolean`: Returns whether the control is valid, and when it is not, fires `invalid`
    * and shows the browser's message at the control.
    * - `setCustomValidity(message: string) => void`: Marks the control invalid with `message`, or clears that with an empty
    * string, as on a native control. The form does not submit while it is set.
-   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
-   * form's `checkValidity()`, as connecting does for the form it starts in.
    *
    * ## CSS Custom Properties
    *
@@ -48748,6 +48750,10 @@ export type CustomElements = {
    * Falling back to what the markup declared rather than to empty, because
    * a restore with no state is a form the browser has nothing recorded for,
    * which is the same situation as a fresh one.
+   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
+   * not. The control shows no message for it: `reportValidity()` does that.
+   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
+   * form's `checkValidity()`, as connecting does for the form it starts in.
    * - `formDisabledCallback(disabled: boolean) => void`: Called by the browser when an ancestor fieldset is disabled or enabled.
    *
    * **The argument is the effective state, and taking it whole is what latched
@@ -48781,15 +48787,11 @@ export type CustomElements = {
    * the fieldset's hold is not recorded. There is no callback to learn it from
    * and reading `:disabled` here would answer about the attribute we are in the
    * middle of removing.
-   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
-   * not. The control shows no message for it: `reportValidity()` does that.
    * - `reportValidity() => boolean`: Returns whether the control is valid, and when it is not, fires `invalid`
    * and shows the browser's message at the control.
    * - `setCustomValidity(message: string) => void`: Marks the control invalid with `message`, or clears that with an empty
    * string, as on a native control. The form does not submit while it is set.
    * - `focus(options?: FocusOptions) => void`: Moves focus to the control, as focusing a native control does.
-   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
-   * form's `checkValidity()`, as connecting does for the form it starts in.
    *
    * ## CSS Custom Properties
    *
@@ -49220,8 +49222,9 @@ export type CustomElements = {
    * submitted nothing and sent no `helix-press`. The control's own click reaches
    * the host's listeners once, retargeted, as one from a native button does. A
    * disabled button does nothing, and a pending one refuses the press.
-   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
-   * form's `checkValidity()`, as connecting does for the form it starts in.
+   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the button's form changes. Its own rather than
+   * an override: the base a button extends watches no form's checks, because
+   * a button reports no verdict of its own.
    * - `formDisabledCallback(disabled: boolean) => void`: Called by the browser when an ancestor fieldset is disabled or enabled.
    *
    * **The argument is the effective state, and taking it whole is what latched
@@ -50104,6 +50107,10 @@ export type CustomElements = {
    * Falling back to what the markup declared rather than to empty, because
    * a restore with no state is a form the browser has nothing recorded for,
    * which is the same situation as a fresh one.
+   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
+   * not. The control shows no message for it: `reportValidity()` does that.
+   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
+   * form's `checkValidity()`, as connecting does for the form it starts in.
    * - `formDisabledCallback(disabled: boolean) => void`: Called by the browser when an ancestor fieldset is disabled or enabled.
    *
    * **The argument is the effective state, and taking it whole is what latched
@@ -50137,14 +50144,10 @@ export type CustomElements = {
    * the fieldset's hold is not recorded. There is no callback to learn it from
    * and reading `:disabled` here would answer about the attribute we are in the
    * middle of removing.
-   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
-   * not. The control shows no message for it: `reportValidity()` does that.
    * - `reportValidity() => boolean`: Returns whether the control is valid, and when it is not, fires `invalid`
    * and shows the browser's message at the control.
    * - `setCustomValidity(message: string) => void`: Marks the control invalid with `message`, or clears that with an empty
    * string, as on a native control. The form does not submit while it is set.
-   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
-   * form's `checkValidity()`, as connecting does for the form it starts in.
    *
    * ## CSS Custom Properties
    *
@@ -50521,6 +50524,10 @@ export type CustomElements = {
    * date picker dialog puts focus. Measured before this: from August 4, two
    * presses of Page Down, Escape, and Down again opened on October 4.
    * A `month` you set stays until the reader pages away from it.
+   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
+   * not. The control shows no message for it: `reportValidity()` does that.
+   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
+   * form's `checkValidity()`, as connecting does for the form it starts in.
    * - `formDisabledCallback(disabled: boolean) => void`: Called by the browser when an ancestor fieldset is disabled or enabled.
    *
    * **The argument is the effective state, and taking it whole is what latched
@@ -50554,14 +50561,10 @@ export type CustomElements = {
    * the fieldset's hold is not recorded. There is no callback to learn it from
    * and reading `:disabled` here would answer about the attribute we are in the
    * middle of removing.
-   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
-   * not. The control shows no message for it: `reportValidity()` does that.
    * - `reportValidity() => boolean`: Returns whether the control is valid, and when it is not, fires `invalid`
    * and shows the browser's message at the control.
    * - `setCustomValidity(message: string) => void`: Marks the control invalid with `message`, or clears that with an empty
    * string, as on a native control. The form does not submit while it is set.
-   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
-   * form's `checkValidity()`, as connecting does for the form it starts in.
    *
    * ## CSS Custom Properties
    *
@@ -52178,6 +52181,10 @@ export type CustomElements = {
    * mechanism a drop uses, so a file put in by dragging and one put in by the
    * picker come back out the same way.
    * - `focus(options?: FocusOptions) => void`: Moves focus to the control, as focusing a native control does.
+   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
+   * not. The control shows no message for it: `reportValidity()` does that.
+   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
+   * form's `checkValidity()`, as connecting does for the form it starts in.
    * - `formDisabledCallback(disabled: boolean) => void`: Called by the browser when an ancestor fieldset is disabled or enabled.
    *
    * **The argument is the effective state, and taking it whole is what latched
@@ -52211,14 +52218,10 @@ export type CustomElements = {
    * the fieldset's hold is not recorded. There is no callback to learn it from
    * and reading `:disabled` here would answer about the attribute we are in the
    * middle of removing.
-   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
-   * not. The control shows no message for it: `reportValidity()` does that.
    * - `reportValidity() => boolean`: Returns whether the control is valid, and when it is not, fires `invalid`
    * and shows the browser's message at the control.
    * - `setCustomValidity(message: string) => void`: Marks the control invalid with `message`, or clears that with an empty
    * string, as on a native control. The form does not submit while it is set.
-   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
-   * form's `checkValidity()`, as connecting does for the form it starts in.
    *
    * ## CSS Custom Properties
    *
@@ -53002,6 +53005,10 @@ export type CustomElements = {
    * which is the same situation as a fresh one.
    * - `setSelectionRange(start: number, end: number, direction?: 'backward' | 'forward' | 'none') => void`: Moves the caret, or selects a run of the text.
    * - `focus(options?: FocusOptions) => void`: Moves focus to the control, as focusing a native control does.
+   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
+   * not. The control shows no message for it: `reportValidity()` does that.
+   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
+   * form's `checkValidity()`, as connecting does for the form it starts in.
    * - `formDisabledCallback(disabled: boolean) => void`: Called by the browser when an ancestor fieldset is disabled or enabled.
    *
    * **The argument is the effective state, and taking it whole is what latched
@@ -53035,14 +53042,10 @@ export type CustomElements = {
    * the fieldset's hold is not recorded. There is no callback to learn it from
    * and reading `:disabled` here would answer about the attribute we are in the
    * middle of removing.
-   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
-   * not. The control shows no message for it: `reportValidity()` does that.
    * - `reportValidity() => boolean`: Returns whether the control is valid, and when it is not, fires `invalid`
    * and shows the browser's message at the control.
    * - `setCustomValidity(message: string) => void`: Marks the control invalid with `message`, or clears that with an empty
    * string, as on a native control. The form does not submit while it is set.
-   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
-   * form's `checkValidity()`, as connecting does for the form it starts in.
    *
    * ## CSS Custom Properties
    *
@@ -54397,8 +54400,9 @@ export type CustomElements = {
    * submitted nothing and sent no `helix-press`. The control's own click reaches
    * the host's listeners once, retargeted, as one from a native button does. A
    * disabled button does nothing, and a pending one refuses the press.
-   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
-   * form's `checkValidity()`, as connecting does for the form it starts in.
+   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the button's form changes. Its own rather than
+   * an override: the base a button extends watches no form's checks, because
+   * a button reports no verdict of its own.
    * - `formDisabledCallback(disabled: boolean) => void`: Called by the browser when an ancestor fieldset is disabled or enabled.
    *
    * **The argument is the effective state, and taking it whole is what latched
@@ -55008,6 +55012,10 @@ export type CustomElements = {
    * method does. It sends no event, as the native method sends none, and it
    * throws `InvalidStateError` on a type with no step, such as `text`.
    * - `stepDown(count = 1) => void`: Moves a number, a date or a time down by `step`, `count` times. See `stepUp`.
+   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
+   * not. The control shows no message for it: `reportValidity()` does that.
+   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
+   * form's `checkValidity()`, as connecting does for the form it starts in.
    * - `formDisabledCallback(disabled: boolean) => void`: Called by the browser when an ancestor fieldset is disabled or enabled.
    *
    * **The argument is the effective state, and taking it whole is what latched
@@ -55041,14 +55049,10 @@ export type CustomElements = {
    * the fieldset's hold is not recorded. There is no callback to learn it from
    * and reading `:disabled` here would answer about the attribute we are in the
    * middle of removing.
-   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
-   * not. The control shows no message for it: `reportValidity()` does that.
    * - `reportValidity() => boolean`: Returns whether the control is valid, and when it is not, fires `invalid`
    * and shows the browser's message at the control.
    * - `setCustomValidity(message: string) => void`: Marks the control invalid with `message`, or clears that with an empty
    * string, as on a native control. The form does not submit while it is set.
-   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
-   * form's `checkValidity()`, as connecting does for the form it starts in.
    *
    * ## CSS Custom Properties
    *
@@ -56682,6 +56686,10 @@ export type CustomElements = {
    * holds: without it the first arrow moved from the top of the list, so Down
    * from 14:07 went to midnight.
    * - `requestFilter(next: string) => boolean`: Requests a new filter, and returns whether the request went through.
+   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
+   * not. The control shows no message for it: `reportValidity()` does that.
+   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
+   * form's `checkValidity()`, as connecting does for the form it starts in.
    * - `formDisabledCallback(disabled: boolean) => void`: Called by the browser when an ancestor fieldset is disabled or enabled.
    *
    * **The argument is the effective state, and taking it whole is what latched
@@ -56715,15 +56723,11 @@ export type CustomElements = {
    * the fieldset's hold is not recorded. There is no callback to learn it from
    * and reading `:disabled` here would answer about the attribute we are in the
    * middle of removing.
-   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
-   * not. The control shows no message for it: `reportValidity()` does that.
    * - `reportValidity() => boolean`: Returns whether the control is valid, and when it is not, fires `invalid`
    * and shows the browser's message at the control.
    * - `setCustomValidity(message: string) => void`: Marks the control invalid with `message`, or clears that with an empty
    * string, as on a native control. The form does not submit while it is set.
    * - `focus(options?: FocusOptions) => void`: Moves focus to the control, as focusing a native control does.
-   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
-   * form's `checkValidity()`, as connecting does for the form it starts in.
    *
    * ## CSS Custom Properties
    *
@@ -59646,6 +59650,10 @@ export type CustomElements = {
    * having to repeat both.
    * - `focus(options?: FocusOptions) => void`: Moves focus to the control, as focusing a native control does.
    * - `select() => void`: Selects the number, so typing replaces it.
+   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
+   * not. The control shows no message for it: `reportValidity()` does that.
+   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
+   * form's `checkValidity()`, as connecting does for the form it starts in.
    * - `formDisabledCallback(disabled: boolean) => void`: Called by the browser when an ancestor fieldset is disabled or enabled.
    *
    * **The argument is the effective state, and taking it whole is what latched
@@ -59679,14 +59687,10 @@ export type CustomElements = {
    * the fieldset's hold is not recorded. There is no callback to learn it from
    * and reading `:disabled` here would answer about the attribute we are in the
    * middle of removing.
-   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
-   * not. The control shows no message for it: `reportValidity()` does that.
    * - `reportValidity() => boolean`: Returns whether the control is valid, and when it is not, fires `invalid`
    * and shows the browser's message at the control.
    * - `setCustomValidity(message: string) => void`: Marks the control invalid with `message`, or clears that with an empty
    * string, as on a native control. The form does not submit while it is set.
-   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
-   * form's `checkValidity()`, as connecting does for the form it starts in.
    *
    * ## CSS Custom Properties
    *
@@ -60896,6 +60900,10 @@ export type CustomElements = {
    * forgetting of a reader's past attempt, whose message otherwise showed over
    * the emptied control the moment the form was reset.
    * - `formStateRestoreCallback(state: string | File | FormData | null) => void`: Takes back the size a browser restores with the form, or the declared one.
+   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
+   * not. The control shows no message for it: `reportValidity()` does that.
+   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
+   * form's `checkValidity()`, as connecting does for the form it starts in.
    * - `formDisabledCallback(disabled: boolean) => void`: Called by the browser when an ancestor fieldset is disabled or enabled.
    *
    * **The argument is the effective state, and taking it whole is what latched
@@ -60929,15 +60937,11 @@ export type CustomElements = {
    * the fieldset's hold is not recorded. There is no callback to learn it from
    * and reading `:disabled` here would answer about the attribute we are in the
    * middle of removing.
-   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
-   * not. The control shows no message for it: `reportValidity()` does that.
    * - `reportValidity() => boolean`: Returns whether the control is valid, and when it is not, fires `invalid`
    * and shows the browser's message at the control.
    * - `setCustomValidity(message: string) => void`: Marks the control invalid with `message`, or clears that with an empty
    * string, as on a native control. The form does not submit while it is set.
    * - `focus(options?: FocusOptions) => void`: Moves focus to the control, as focusing a native control does.
-   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
-   * form's `checkValidity()`, as connecting does for the form it starts in.
    *
    * ## CSS Custom Properties
    *
@@ -61244,6 +61248,10 @@ export type CustomElements = {
    * which is the same situation as a fresh one.
    * - `focus(options?: FocusOptions) => void`: Moves focus to the control, as focusing a native control does.
    * - `clear() => void`: Empties every box and puts the caret in the first.
+   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
+   * not. The control shows no message for it: `reportValidity()` does that.
+   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
+   * form's `checkValidity()`, as connecting does for the form it starts in.
    * - `formDisabledCallback(disabled: boolean) => void`: Called by the browser when an ancestor fieldset is disabled or enabled.
    *
    * **The argument is the effective state, and taking it whole is what latched
@@ -61277,14 +61285,10 @@ export type CustomElements = {
    * the fieldset's hold is not recorded. There is no callback to learn it from
    * and reading `:disabled` here would answer about the attribute we are in the
    * middle of removing.
-   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
-   * not. The control shows no message for it: `reportValidity()` does that.
    * - `reportValidity() => boolean`: Returns whether the control is valid, and when it is not, fires `invalid`
    * and shows the browser's message at the control.
    * - `setCustomValidity(message: string) => void`: Marks the control invalid with `message`, or clears that with an empty
    * string, as on a native control. The form does not submit while it is set.
-   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
-   * form's `checkValidity()`, as connecting does for the form it starts in.
    *
    * ## CSS Custom Properties
    *
@@ -62042,6 +62046,10 @@ export type CustomElements = {
    * Falling back to what the markup declared rather than to empty, because
    * a restore with no state is a form the browser has nothing recorded for,
    * which is the same situation as a fresh one.
+   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
+   * not. The control shows no message for it: `reportValidity()` does that.
+   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
+   * form's `checkValidity()`, as connecting does for the form it starts in.
    * - `formDisabledCallback(disabled: boolean) => void`: Called by the browser when an ancestor fieldset is disabled or enabled.
    *
    * **The argument is the effective state, and taking it whole is what latched
@@ -62075,15 +62083,11 @@ export type CustomElements = {
    * the fieldset's hold is not recorded. There is no callback to learn it from
    * and reading `:disabled` here would answer about the attribute we are in the
    * middle of removing.
-   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
-   * not. The control shows no message for it: `reportValidity()` does that.
    * - `reportValidity() => boolean`: Returns whether the control is valid, and when it is not, fires `invalid`
    * and shows the browser's message at the control.
    * - `setCustomValidity(message: string) => void`: Marks the control invalid with `message`, or clears that with an empty
    * string, as on a native control. The form does not submit while it is set.
    * - `focus(options?: FocusOptions) => void`: Moves focus to the control, as focusing a native control does.
-   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
-   * form's `checkValidity()`, as connecting does for the form it starts in.
    *
    * ## CSS Custom Properties
    *
@@ -62543,6 +62547,10 @@ export type CustomElements = {
    * Falling back to what the markup declared rather than to empty, because
    * a restore with no state is a form the browser has nothing recorded for,
    * which is the same situation as a fresh one.
+   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
+   * not. The control shows no message for it: `reportValidity()` does that.
+   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
+   * form's `checkValidity()`, as connecting does for the form it starts in.
    * - `formDisabledCallback(disabled: boolean) => void`: Called by the browser when an ancestor fieldset is disabled or enabled.
    *
    * **The argument is the effective state, and taking it whole is what latched
@@ -62576,15 +62584,11 @@ export type CustomElements = {
    * the fieldset's hold is not recorded. There is no callback to learn it from
    * and reading `:disabled` here would answer about the attribute we are in the
    * middle of removing.
-   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
-   * not. The control shows no message for it: `reportValidity()` does that.
    * - `reportValidity() => boolean`: Returns whether the control is valid, and when it is not, fires `invalid`
    * and shows the browser's message at the control.
    * - `setCustomValidity(message: string) => void`: Marks the control invalid with `message`, or clears that with an empty
    * string, as on a native control. The form does not submit while it is set.
    * - `focus(options?: FocusOptions) => void`: Moves focus to the control, as focusing a native control does.
-   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
-   * form's `checkValidity()`, as connecting does for the form it starts in.
    *
    * ## CSS Custom Properties
    *
@@ -64154,6 +64158,10 @@ export type CustomElements = {
    * a restore with no state is a form the browser has nothing recorded for,
    * which is the same situation as a fresh one.
    * - `focus(options?: FocusOptions) => void`: Moves focus to the control, as focusing a native control does.
+   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
+   * not. The control shows no message for it: `reportValidity()` does that.
+   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
+   * form's `checkValidity()`, as connecting does for the form it starts in.
    * - `formDisabledCallback(disabled: boolean) => void`: Called by the browser when an ancestor fieldset is disabled or enabled.
    *
    * **The argument is the effective state, and taking it whole is what latched
@@ -64187,14 +64195,10 @@ export type CustomElements = {
    * the fieldset's hold is not recorded. There is no callback to learn it from
    * and reading `:disabled` here would answer about the attribute we are in the
    * middle of removing.
-   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
-   * not. The control shows no message for it: `reportValidity()` does that.
    * - `reportValidity() => boolean`: Returns whether the control is valid, and when it is not, fires `invalid`
    * and shows the browser's message at the control.
    * - `setCustomValidity(message: string) => void`: Marks the control invalid with `message`, or clears that with an empty
    * string, as on a native control. The form does not submit while it is set.
-   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
-   * form's `checkValidity()`, as connecting does for the form it starts in.
    *
    * ## CSS Custom Properties
    *
@@ -64655,6 +64659,10 @@ export type CustomElements = {
    * Falling back to what the markup declared rather than to empty, because
    * a restore with no state is a form the browser has nothing recorded for,
    * which is the same situation as a fresh one.
+   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
+   * not. The control shows no message for it: `reportValidity()` does that.
+   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
+   * form's `checkValidity()`, as connecting does for the form it starts in.
    * - `formDisabledCallback(disabled: boolean) => void`: Called by the browser when an ancestor fieldset is disabled or enabled.
    *
    * **The argument is the effective state, and taking it whole is what latched
@@ -64688,15 +64696,11 @@ export type CustomElements = {
    * the fieldset's hold is not recorded. There is no callback to learn it from
    * and reading `:disabled` here would answer about the attribute we are in the
    * middle of removing.
-   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
-   * not. The control shows no message for it: `reportValidity()` does that.
    * - `reportValidity() => boolean`: Returns whether the control is valid, and when it is not, fires `invalid`
    * and shows the browser's message at the control.
    * - `setCustomValidity(message: string) => void`: Marks the control invalid with `message`, or clears that with an empty
    * string, as on a native control. The form does not submit while it is set.
    * - `focus(options?: FocusOptions) => void`: Moves focus to the control, as focusing a native control does.
-   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
-   * form's `checkValidity()`, as connecting does for the form it starts in.
    *
    * ## CSS Custom Properties
    *
@@ -66383,6 +66387,10 @@ export type CustomElements = {
    * - `click() => void`: Turns the switch on or off, as `click()` does a native checkbox: passed to the control
    * inside, so the one click a listener hears is the control's, after it has
    * moved. See `HostClickController`.
+   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
+   * not. The control shows no message for it: `reportValidity()` does that.
+   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
+   * form's `checkValidity()`, as connecting does for the form it starts in.
    * - `formDisabledCallback(disabled: boolean) => void`: Called by the browser when an ancestor fieldset is disabled or enabled.
    *
    * **The argument is the effective state, and taking it whole is what latched
@@ -66416,15 +66424,11 @@ export type CustomElements = {
    * the fieldset's hold is not recorded. There is no callback to learn it from
    * and reading `:disabled` here would answer about the attribute we are in the
    * middle of removing.
-   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
-   * not. The control shows no message for it: `reportValidity()` does that.
    * - `reportValidity() => boolean`: Returns whether the control is valid, and when it is not, fires `invalid`
    * and shows the browser's message at the control.
    * - `setCustomValidity(message: string) => void`: Marks the control invalid with `message`, or clears that with an empty
    * string, as on a native control. The form does not submit while it is set.
    * - `focus(options?: FocusOptions) => void`: Moves focus to the control, as focusing a native control does.
-   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
-   * form's `checkValidity()`, as connecting does for the form it starts in.
    *
    * ## CSS Custom Properties
    *
@@ -68008,6 +68012,10 @@ export type CustomElements = {
    * selected after. It sends no event, as the native method sends none.
    * - `select() => void`: Selects everything in the field.
    * - `focus(options?: FocusOptions) => void`: Moves focus to the control, as focusing a native control does.
+   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
+   * not. The control shows no message for it: `reportValidity()` does that.
+   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
+   * form's `checkValidity()`, as connecting does for the form it starts in.
    * - `formDisabledCallback(disabled: boolean) => void`: Called by the browser when an ancestor fieldset is disabled or enabled.
    *
    * **The argument is the effective state, and taking it whole is what latched
@@ -68041,14 +68049,10 @@ export type CustomElements = {
    * the fieldset's hold is not recorded. There is no callback to learn it from
    * and reading `:disabled` here would answer about the attribute we are in the
    * middle of removing.
-   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
-   * not. The control shows no message for it: `reportValidity()` does that.
    * - `reportValidity() => boolean`: Returns whether the control is valid, and when it is not, fires `invalid`
    * and shows the browser's message at the control.
    * - `setCustomValidity(message: string) => void`: Marks the control invalid with `message`, or clears that with an empty
    * string, as on a native control. The form does not submit while it is set.
-   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
-   * form's `checkValidity()`, as connecting does for the form it starts in.
    *
    * ## CSS Custom Properties
    *
@@ -68375,6 +68379,10 @@ export type CustomElements = {
    * Falling back to what the markup declared rather than to empty, because
    * a restore with no state is a form the browser has nothing recorded for,
    * which is the same situation as a fresh one.
+   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
+   * not. The control shows no message for it: `reportValidity()` does that.
+   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
+   * form's `checkValidity()`, as connecting does for the form it starts in.
    * - `formDisabledCallback(disabled: boolean) => void`: Called by the browser when an ancestor fieldset is disabled or enabled.
    *
    * **The argument is the effective state, and taking it whole is what latched
@@ -68408,14 +68416,10 @@ export type CustomElements = {
    * the fieldset's hold is not recorded. There is no callback to learn it from
    * and reading `:disabled` here would answer about the attribute we are in the
    * middle of removing.
-   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
-   * not. The control shows no message for it: `reportValidity()` does that.
    * - `reportValidity() => boolean`: Returns whether the control is valid, and when it is not, fires `invalid`
    * and shows the browser's message at the control.
    * - `setCustomValidity(message: string) => void`: Marks the control invalid with `message`, or clears that with an empty
    * string, as on a native control. The form does not submit while it is set.
-   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
-   * form's `checkValidity()`, as connecting does for the form it starts in.
    *
    * ## CSS Custom Properties
    *
@@ -68834,6 +68838,10 @@ export type CustomElements = {
    * calls this again afterwards. The guard below makes the early call harmless
    * rather than wrong, which is why it can be left in.
    * - `focus(options?: FocusOptions) => void`: Moves focus to the control, as focusing a native control does.
+   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
+   * not. The control shows no message for it: `reportValidity()` does that.
+   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
+   * form's `checkValidity()`, as connecting does for the form it starts in.
    * - `formDisabledCallback(disabled: boolean) => void`: Called by the browser when an ancestor fieldset is disabled or enabled.
    *
    * **The argument is the effective state, and taking it whole is what latched
@@ -68867,14 +68875,10 @@ export type CustomElements = {
    * the fieldset's hold is not recorded. There is no callback to learn it from
    * and reading `:disabled` here would answer about the attribute we are in the
    * middle of removing.
-   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
-   * not. The control shows no message for it: `reportValidity()` does that.
    * - `reportValidity() => boolean`: Returns whether the control is valid, and when it is not, fires `invalid`
    * and shows the browser's message at the control.
    * - `setCustomValidity(message: string) => void`: Marks the control invalid with `message`, or clears that with an empty
    * string, as on a native control. The form does not submit while it is set.
-   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
-   * form's `checkValidity()`, as connecting does for the form it starts in.
    *
    * ## CSS Custom Properties
    *
@@ -69650,6 +69654,10 @@ export type CustomElements = {
    * Falling back to what the markup declared rather than to empty, because
    * a restore with no state is a form the browser has nothing recorded for,
    * which is the same situation as a fresh one.
+   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
+   * not. The control shows no message for it: `reportValidity()` does that.
+   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
+   * form's `checkValidity()`, as connecting does for the form it starts in.
    * - `formDisabledCallback(disabled: boolean) => void`: Called by the browser when an ancestor fieldset is disabled or enabled.
    *
    * **The argument is the effective state, and taking it whole is what latched
@@ -69683,15 +69691,11 @@ export type CustomElements = {
    * the fieldset's hold is not recorded. There is no callback to learn it from
    * and reading `:disabled` here would answer about the attribute we are in the
    * middle of removing.
-   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
-   * not. The control shows no message for it: `reportValidity()` does that.
    * - `reportValidity() => boolean`: Returns whether the control is valid, and when it is not, fires `invalid`
    * and shows the browser's message at the control.
    * - `setCustomValidity(message: string) => void`: Marks the control invalid with `message`, or clears that with an empty
    * string, as on a native control. The form does not submit while it is set.
    * - `focus(options?: FocusOptions) => void`: Moves focus to the control, as focusing a native control does.
-   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
-   * form's `checkValidity()`, as connecting does for the form it starts in.
    *
    * ## CSS Custom Properties
    *
@@ -74629,7 +74633,9 @@ export type CustomElementsSolidJs = {
    * submitted nothing and sent no `helix-press`. The control's own click reaches
    * the host's listeners once, retargeted, as one from a native button does. A
    * disabled button does nothing, and a pending one refuses the press.
-   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the button's form changes.
+   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the button's form changes. Its own rather than
+   * an override: the base a button extends watches no form's checks, because
+   * a button reports no verdict of its own.
    * - `formDisabledCallback(disabled: boolean) => void`: Called by the browser when an ancestor fieldset is disabled or enabled.
    *
    * **The argument is the effective state, and taking it whole is what latched
@@ -76184,6 +76190,10 @@ export type CustomElementsSolidJs = {
    * forgetting of a reader's past attempt, whose message otherwise showed over
    * the emptied control the moment the form was reset.
    * - `formStateRestoreCallback(state: string | File | FormData | null) => void`: Brings back the draft when the browser restores the form.
+   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
+   * not. The control shows no message for it: `reportValidity()` does that.
+   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
+   * form's `checkValidity()`, as connecting does for the form it starts in.
    * - `formDisabledCallback(disabled: boolean) => void`: Called by the browser when an ancestor fieldset is disabled or enabled.
    *
    * **The argument is the effective state, and taking it whole is what latched
@@ -76217,15 +76227,11 @@ export type CustomElementsSolidJs = {
    * the fieldset's hold is not recorded. There is no callback to learn it from
    * and reading `:disabled` here would answer about the attribute we are in the
    * middle of removing.
-   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
-   * not. The control shows no message for it: `reportValidity()` does that.
    * - `reportValidity() => boolean`: Returns whether the control is valid, and when it is not, fires `invalid`
    * and shows the browser's message at the control.
    * - `setCustomValidity(message: string) => void`: Marks the control invalid with `message`, or clears that with an empty
    * string, as on a native control. The form does not submit while it is set.
    * - `focus(options?: FocusOptions) => void`: Moves focus to the control, as focusing a native control does.
-   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
-   * form's `checkValidity()`, as connecting does for the form it starts in.
    *
    * ## CSS Custom Properties
    *
@@ -76757,6 +76763,10 @@ export type CustomElementsSolidJs = {
    *
    * Through the base's prototype rather than `super`, because the base this
    * grafts onto is any element and only a form element has the hook.
+   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
+   * not. The control shows no message for it: `reportValidity()` does that.
+   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
+   * form's `checkValidity()`, as connecting does for the form it starts in.
    * - `formDisabledCallback(disabled: boolean) => void`: Called by the browser when an ancestor fieldset is disabled or enabled.
    *
    * **The argument is the effective state, and taking it whole is what latched
@@ -76790,15 +76800,11 @@ export type CustomElementsSolidJs = {
    * the fieldset's hold is not recorded. There is no callback to learn it from
    * and reading `:disabled` here would answer about the attribute we are in the
    * middle of removing.
-   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
-   * not. The control shows no message for it: `reportValidity()` does that.
    * - `reportValidity() => boolean`: Returns whether the control is valid, and when it is not, fires `invalid`
    * and shows the browser's message at the control.
    * - `setCustomValidity(message: string) => void`: Marks the control invalid with `message`, or clears that with an empty
    * string, as on a native control. The form does not submit while it is set.
    * - `focus(options?: FocusOptions) => void`: Moves focus to the control, as focusing a native control does.
-   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
-   * form's `checkValidity()`, as connecting does for the form it starts in.
    *
    * ## CSS Custom Properties
    *
@@ -77046,6 +77052,10 @@ export type CustomElementsSolidJs = {
    * - `click() => void`: Ticks or clears the box, as `click()` does a native checkbox: passed to the control
    * inside, so the one click a listener hears is the control's, after it has
    * moved. See `HostClickController`.
+   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
+   * not. The control shows no message for it: `reportValidity()` does that.
+   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
+   * form's `checkValidity()`, as connecting does for the form it starts in.
    * - `formDisabledCallback(disabled: boolean) => void`: Called by the browser when an ancestor fieldset is disabled or enabled.
    *
    * **The argument is the effective state, and taking it whole is what latched
@@ -77079,15 +77089,11 @@ export type CustomElementsSolidJs = {
    * the fieldset's hold is not recorded. There is no callback to learn it from
    * and reading `:disabled` here would answer about the attribute we are in the
    * middle of removing.
-   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
-   * not. The control shows no message for it: `reportValidity()` does that.
    * - `reportValidity() => boolean`: Returns whether the control is valid, and when it is not, fires `invalid`
    * and shows the browser's message at the control.
    * - `setCustomValidity(message: string) => void`: Marks the control invalid with `message`, or clears that with an empty
    * string, as on a native control. The form does not submit while it is set.
    * - `focus(options?: FocusOptions) => void`: Moves focus to the control, as focusing a native control does.
-   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
-   * form's `checkValidity()`, as connecting does for the form it starts in.
    *
    * ## CSS Custom Properties
    *
@@ -77707,6 +77713,10 @@ export type CustomElementsSolidJs = {
    * Falling back to what the markup declared rather than to empty, because
    * a restore with no state is a form the browser has nothing recorded for,
    * which is the same situation as a fresh one.
+   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
+   * not. The control shows no message for it: `reportValidity()` does that.
+   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
+   * form's `checkValidity()`, as connecting does for the form it starts in.
    * - `formDisabledCallback(disabled: boolean) => void`: Called by the browser when an ancestor fieldset is disabled or enabled.
    *
    * **The argument is the effective state, and taking it whole is what latched
@@ -77740,14 +77750,10 @@ export type CustomElementsSolidJs = {
    * the fieldset's hold is not recorded. There is no callback to learn it from
    * and reading `:disabled` here would answer about the attribute we are in the
    * middle of removing.
-   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
-   * not. The control shows no message for it: `reportValidity()` does that.
    * - `reportValidity() => boolean`: Returns whether the control is valid, and when it is not, fires `invalid`
    * and shows the browser's message at the control.
    * - `setCustomValidity(message: string) => void`: Marks the control invalid with `message`, or clears that with an empty
    * string, as on a native control. The form does not submit while it is set.
-   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
-   * form's `checkValidity()`, as connecting does for the form it starts in.
    *
    * ## CSS Custom Properties
    *
@@ -78122,6 +78128,10 @@ export type CustomElementsSolidJs = {
    * a restore with no state is a form the browser has nothing recorded for,
    * which is the same situation as a fresh one.
    * - `focus(options?: FocusOptions) => void`: Moves focus to the control, as focusing a native control does.
+   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
+   * not. The control shows no message for it: `reportValidity()` does that.
+   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
+   * form's `checkValidity()`, as connecting does for the form it starts in.
    * - `formDisabledCallback(disabled: boolean) => void`: Called by the browser when an ancestor fieldset is disabled or enabled.
    *
    * **The argument is the effective state, and taking it whole is what latched
@@ -78155,14 +78165,10 @@ export type CustomElementsSolidJs = {
    * the fieldset's hold is not recorded. There is no callback to learn it from
    * and reading `:disabled` here would answer about the attribute we are in the
    * middle of removing.
-   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
-   * not. The control shows no message for it: `reportValidity()` does that.
    * - `reportValidity() => boolean`: Returns whether the control is valid, and when it is not, fires `invalid`
    * and shows the browser's message at the control.
    * - `setCustomValidity(message: string) => void`: Marks the control invalid with `message`, or clears that with an empty
    * string, as on a native control. The form does not submit while it is set.
-   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
-   * form's `checkValidity()`, as connecting does for the form it starts in.
    *
    * ## CSS Custom Properties
    *
@@ -78544,6 +78550,10 @@ export type CustomElementsSolidJs = {
    * Falling back to what the markup declared rather than to empty, because
    * a restore with no state is a form the browser has nothing recorded for,
    * which is the same situation as a fresh one.
+   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
+   * not. The control shows no message for it: `reportValidity()` does that.
+   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
+   * form's `checkValidity()`, as connecting does for the form it starts in.
    * - `formDisabledCallback(disabled: boolean) => void`: Called by the browser when an ancestor fieldset is disabled or enabled.
    *
    * **The argument is the effective state, and taking it whole is what latched
@@ -78577,15 +78587,11 @@ export type CustomElementsSolidJs = {
    * the fieldset's hold is not recorded. There is no callback to learn it from
    * and reading `:disabled` here would answer about the attribute we are in the
    * middle of removing.
-   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
-   * not. The control shows no message for it: `reportValidity()` does that.
    * - `reportValidity() => boolean`: Returns whether the control is valid, and when it is not, fires `invalid`
    * and shows the browser's message at the control.
    * - `setCustomValidity(message: string) => void`: Marks the control invalid with `message`, or clears that with an empty
    * string, as on a native control. The form does not submit while it is set.
    * - `focus(options?: FocusOptions) => void`: Moves focus to the control, as focusing a native control does.
-   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
-   * form's `checkValidity()`, as connecting does for the form it starts in.
    *
    * ## CSS Custom Properties
    *
@@ -79022,8 +79028,9 @@ export type CustomElementsSolidJs = {
    * submitted nothing and sent no `helix-press`. The control's own click reaches
    * the host's listeners once, retargeted, as one from a native button does. A
    * disabled button does nothing, and a pending one refuses the press.
-   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
-   * form's `checkValidity()`, as connecting does for the form it starts in.
+   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the button's form changes. Its own rather than
+   * an override: the base a button extends watches no form's checks, because
+   * a button reports no verdict of its own.
    * - `formDisabledCallback(disabled: boolean) => void`: Called by the browser when an ancestor fieldset is disabled or enabled.
    *
    * **The argument is the effective state, and taking it whole is what latched
@@ -79912,6 +79919,10 @@ export type CustomElementsSolidJs = {
    * Falling back to what the markup declared rather than to empty, because
    * a restore with no state is a form the browser has nothing recorded for,
    * which is the same situation as a fresh one.
+   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
+   * not. The control shows no message for it: `reportValidity()` does that.
+   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
+   * form's `checkValidity()`, as connecting does for the form it starts in.
    * - `formDisabledCallback(disabled: boolean) => void`: Called by the browser when an ancestor fieldset is disabled or enabled.
    *
    * **The argument is the effective state, and taking it whole is what latched
@@ -79945,14 +79956,10 @@ export type CustomElementsSolidJs = {
    * the fieldset's hold is not recorded. There is no callback to learn it from
    * and reading `:disabled` here would answer about the attribute we are in the
    * middle of removing.
-   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
-   * not. The control shows no message for it: `reportValidity()` does that.
    * - `reportValidity() => boolean`: Returns whether the control is valid, and when it is not, fires `invalid`
    * and shows the browser's message at the control.
    * - `setCustomValidity(message: string) => void`: Marks the control invalid with `message`, or clears that with an empty
    * string, as on a native control. The form does not submit while it is set.
-   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
-   * form's `checkValidity()`, as connecting does for the form it starts in.
    *
    * ## CSS Custom Properties
    *
@@ -80332,6 +80339,10 @@ export type CustomElementsSolidJs = {
    * date picker dialog puts focus. Measured before this: from August 4, two
    * presses of Page Down, Escape, and Down again opened on October 4.
    * A `month` you set stays until the reader pages away from it.
+   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
+   * not. The control shows no message for it: `reportValidity()` does that.
+   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
+   * form's `checkValidity()`, as connecting does for the form it starts in.
    * - `formDisabledCallback(disabled: boolean) => void`: Called by the browser when an ancestor fieldset is disabled or enabled.
    *
    * **The argument is the effective state, and taking it whole is what latched
@@ -80365,14 +80376,10 @@ export type CustomElementsSolidJs = {
    * the fieldset's hold is not recorded. There is no callback to learn it from
    * and reading `:disabled` here would answer about the attribute we are in the
    * middle of removing.
-   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
-   * not. The control shows no message for it: `reportValidity()` does that.
    * - `reportValidity() => boolean`: Returns whether the control is valid, and when it is not, fires `invalid`
    * and shows the browser's message at the control.
    * - `setCustomValidity(message: string) => void`: Marks the control invalid with `message`, or clears that with an empty
    * string, as on a native control. The form does not submit while it is set.
-   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
-   * form's `checkValidity()`, as connecting does for the form it starts in.
    *
    * ## CSS Custom Properties
    *
@@ -82019,6 +82026,10 @@ export type CustomElementsSolidJs = {
    * mechanism a drop uses, so a file put in by dragging and one put in by the
    * picker come back out the same way.
    * - `focus(options?: FocusOptions) => void`: Moves focus to the control, as focusing a native control does.
+   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
+   * not. The control shows no message for it: `reportValidity()` does that.
+   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
+   * form's `checkValidity()`, as connecting does for the form it starts in.
    * - `formDisabledCallback(disabled: boolean) => void`: Called by the browser when an ancestor fieldset is disabled or enabled.
    *
    * **The argument is the effective state, and taking it whole is what latched
@@ -82052,14 +82063,10 @@ export type CustomElementsSolidJs = {
    * the fieldset's hold is not recorded. There is no callback to learn it from
    * and reading `:disabled` here would answer about the attribute we are in the
    * middle of removing.
-   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
-   * not. The control shows no message for it: `reportValidity()` does that.
    * - `reportValidity() => boolean`: Returns whether the control is valid, and when it is not, fires `invalid`
    * and shows the browser's message at the control.
    * - `setCustomValidity(message: string) => void`: Marks the control invalid with `message`, or clears that with an empty
    * string, as on a native control. The form does not submit while it is set.
-   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
-   * form's `checkValidity()`, as connecting does for the form it starts in.
    *
    * ## CSS Custom Properties
    *
@@ -82858,6 +82865,10 @@ export type CustomElementsSolidJs = {
    * which is the same situation as a fresh one.
    * - `setSelectionRange(start: number, end: number, direction?: 'backward' | 'forward' | 'none') => void`: Moves the caret, or selects a run of the text.
    * - `focus(options?: FocusOptions) => void`: Moves focus to the control, as focusing a native control does.
+   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
+   * not. The control shows no message for it: `reportValidity()` does that.
+   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
+   * form's `checkValidity()`, as connecting does for the form it starts in.
    * - `formDisabledCallback(disabled: boolean) => void`: Called by the browser when an ancestor fieldset is disabled or enabled.
    *
    * **The argument is the effective state, and taking it whole is what latched
@@ -82891,14 +82902,10 @@ export type CustomElementsSolidJs = {
    * the fieldset's hold is not recorded. There is no callback to learn it from
    * and reading `:disabled` here would answer about the attribute we are in the
    * middle of removing.
-   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
-   * not. The control shows no message for it: `reportValidity()` does that.
    * - `reportValidity() => boolean`: Returns whether the control is valid, and when it is not, fires `invalid`
    * and shows the browser's message at the control.
    * - `setCustomValidity(message: string) => void`: Marks the control invalid with `message`, or clears that with an empty
    * string, as on a native control. The form does not submit while it is set.
-   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
-   * form's `checkValidity()`, as connecting does for the form it starts in.
    *
    * ## CSS Custom Properties
    *
@@ -84271,8 +84278,9 @@ export type CustomElementsSolidJs = {
    * submitted nothing and sent no `helix-press`. The control's own click reaches
    * the host's listeners once, retargeted, as one from a native button does. A
    * disabled button does nothing, and a pending one refuses the press.
-   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
-   * form's `checkValidity()`, as connecting does for the form it starts in.
+   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the button's form changes. Its own rather than
+   * an override: the base a button extends watches no form's checks, because
+   * a button reports no verdict of its own.
    * - `formDisabledCallback(disabled: boolean) => void`: Called by the browser when an ancestor fieldset is disabled or enabled.
    *
    * **The argument is the effective state, and taking it whole is what latched
@@ -84892,6 +84900,10 @@ export type CustomElementsSolidJs = {
    * method does. It sends no event, as the native method sends none, and it
    * throws `InvalidStateError` on a type with no step, such as `text`.
    * - `stepDown(count = 1) => void`: Moves a number, a date or a time down by `step`, `count` times. See `stepUp`.
+   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
+   * not. The control shows no message for it: `reportValidity()` does that.
+   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
+   * form's `checkValidity()`, as connecting does for the form it starts in.
    * - `formDisabledCallback(disabled: boolean) => void`: Called by the browser when an ancestor fieldset is disabled or enabled.
    *
    * **The argument is the effective state, and taking it whole is what latched
@@ -84925,14 +84937,10 @@ export type CustomElementsSolidJs = {
    * the fieldset's hold is not recorded. There is no callback to learn it from
    * and reading `:disabled` here would answer about the attribute we are in the
    * middle of removing.
-   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
-   * not. The control shows no message for it: `reportValidity()` does that.
    * - `reportValidity() => boolean`: Returns whether the control is valid, and when it is not, fires `invalid`
    * and shows the browser's message at the control.
    * - `setCustomValidity(message: string) => void`: Marks the control invalid with `message`, or clears that with an empty
    * string, as on a native control. The form does not submit while it is set.
-   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
-   * form's `checkValidity()`, as connecting does for the form it starts in.
    *
    * ## CSS Custom Properties
    *
@@ -86590,6 +86598,10 @@ export type CustomElementsSolidJs = {
    * holds: without it the first arrow moved from the top of the list, so Down
    * from 14:07 went to midnight.
    * - `requestFilter(next: string) => boolean`: Requests a new filter, and returns whether the request went through.
+   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
+   * not. The control shows no message for it: `reportValidity()` does that.
+   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
+   * form's `checkValidity()`, as connecting does for the form it starts in.
    * - `formDisabledCallback(disabled: boolean) => void`: Called by the browser when an ancestor fieldset is disabled or enabled.
    *
    * **The argument is the effective state, and taking it whole is what latched
@@ -86623,15 +86635,11 @@ export type CustomElementsSolidJs = {
    * the fieldset's hold is not recorded. There is no callback to learn it from
    * and reading `:disabled` here would answer about the attribute we are in the
    * middle of removing.
-   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
-   * not. The control shows no message for it: `reportValidity()` does that.
    * - `reportValidity() => boolean`: Returns whether the control is valid, and when it is not, fires `invalid`
    * and shows the browser's message at the control.
    * - `setCustomValidity(message: string) => void`: Marks the control invalid with `message`, or clears that with an empty
    * string, as on a native control. The form does not submit while it is set.
    * - `focus(options?: FocusOptions) => void`: Moves focus to the control, as focusing a native control does.
-   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
-   * form's `checkValidity()`, as connecting does for the form it starts in.
    *
    * ## CSS Custom Properties
    *
@@ -89620,6 +89628,10 @@ export type CustomElementsSolidJs = {
    * having to repeat both.
    * - `focus(options?: FocusOptions) => void`: Moves focus to the control, as focusing a native control does.
    * - `select() => void`: Selects the number, so typing replaces it.
+   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
+   * not. The control shows no message for it: `reportValidity()` does that.
+   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
+   * form's `checkValidity()`, as connecting does for the form it starts in.
    * - `formDisabledCallback(disabled: boolean) => void`: Called by the browser when an ancestor fieldset is disabled or enabled.
    *
    * **The argument is the effective state, and taking it whole is what latched
@@ -89653,14 +89665,10 @@ export type CustomElementsSolidJs = {
    * the fieldset's hold is not recorded. There is no callback to learn it from
    * and reading `:disabled` here would answer about the attribute we are in the
    * middle of removing.
-   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
-   * not. The control shows no message for it: `reportValidity()` does that.
    * - `reportValidity() => boolean`: Returns whether the control is valid, and when it is not, fires `invalid`
    * and shows the browser's message at the control.
    * - `setCustomValidity(message: string) => void`: Marks the control invalid with `message`, or clears that with an empty
    * string, as on a native control. The form does not submit while it is set.
-   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
-   * form's `checkValidity()`, as connecting does for the form it starts in.
    *
    * ## CSS Custom Properties
    *
@@ -90893,6 +90901,10 @@ export type CustomElementsSolidJs = {
    * forgetting of a reader's past attempt, whose message otherwise showed over
    * the emptied control the moment the form was reset.
    * - `formStateRestoreCallback(state: string | File | FormData | null) => void`: Takes back the size a browser restores with the form, or the declared one.
+   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
+   * not. The control shows no message for it: `reportValidity()` does that.
+   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
+   * form's `checkValidity()`, as connecting does for the form it starts in.
    * - `formDisabledCallback(disabled: boolean) => void`: Called by the browser when an ancestor fieldset is disabled or enabled.
    *
    * **The argument is the effective state, and taking it whole is what latched
@@ -90926,15 +90938,11 @@ export type CustomElementsSolidJs = {
    * the fieldset's hold is not recorded. There is no callback to learn it from
    * and reading `:disabled` here would answer about the attribute we are in the
    * middle of removing.
-   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
-   * not. The control shows no message for it: `reportValidity()` does that.
    * - `reportValidity() => boolean`: Returns whether the control is valid, and when it is not, fires `invalid`
    * and shows the browser's message at the control.
    * - `setCustomValidity(message: string) => void`: Marks the control invalid with `message`, or clears that with an empty
    * string, as on a native control. The form does not submit while it is set.
    * - `focus(options?: FocusOptions) => void`: Moves focus to the control, as focusing a native control does.
-   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
-   * form's `checkValidity()`, as connecting does for the form it starts in.
    *
    * ## CSS Custom Properties
    *
@@ -91247,6 +91255,10 @@ export type CustomElementsSolidJs = {
    * which is the same situation as a fresh one.
    * - `focus(options?: FocusOptions) => void`: Moves focus to the control, as focusing a native control does.
    * - `clear() => void`: Empties every box and puts the caret in the first.
+   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
+   * not. The control shows no message for it: `reportValidity()` does that.
+   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
+   * form's `checkValidity()`, as connecting does for the form it starts in.
    * - `formDisabledCallback(disabled: boolean) => void`: Called by the browser when an ancestor fieldset is disabled or enabled.
    *
    * **The argument is the effective state, and taking it whole is what latched
@@ -91280,14 +91292,10 @@ export type CustomElementsSolidJs = {
    * the fieldset's hold is not recorded. There is no callback to learn it from
    * and reading `:disabled` here would answer about the attribute we are in the
    * middle of removing.
-   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
-   * not. The control shows no message for it: `reportValidity()` does that.
    * - `reportValidity() => boolean`: Returns whether the control is valid, and when it is not, fires `invalid`
    * and shows the browser's message at the control.
    * - `setCustomValidity(message: string) => void`: Marks the control invalid with `message`, or clears that with an empty
    * string, as on a native control. The form does not submit while it is set.
-   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
-   * form's `checkValidity()`, as connecting does for the form it starts in.
    *
    * ## CSS Custom Properties
    *
@@ -92062,6 +92070,10 @@ export type CustomElementsSolidJs = {
    * Falling back to what the markup declared rather than to empty, because
    * a restore with no state is a form the browser has nothing recorded for,
    * which is the same situation as a fresh one.
+   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
+   * not. The control shows no message for it: `reportValidity()` does that.
+   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
+   * form's `checkValidity()`, as connecting does for the form it starts in.
    * - `formDisabledCallback(disabled: boolean) => void`: Called by the browser when an ancestor fieldset is disabled or enabled.
    *
    * **The argument is the effective state, and taking it whole is what latched
@@ -92095,15 +92107,11 @@ export type CustomElementsSolidJs = {
    * the fieldset's hold is not recorded. There is no callback to learn it from
    * and reading `:disabled` here would answer about the attribute we are in the
    * middle of removing.
-   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
-   * not. The control shows no message for it: `reportValidity()` does that.
    * - `reportValidity() => boolean`: Returns whether the control is valid, and when it is not, fires `invalid`
    * and shows the browser's message at the control.
    * - `setCustomValidity(message: string) => void`: Marks the control invalid with `message`, or clears that with an empty
    * string, as on a native control. The form does not submit while it is set.
    * - `focus(options?: FocusOptions) => void`: Moves focus to the control, as focusing a native control does.
-   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
-   * form's `checkValidity()`, as connecting does for the form it starts in.
    *
    * ## CSS Custom Properties
    *
@@ -92571,6 +92579,10 @@ export type CustomElementsSolidJs = {
    * Falling back to what the markup declared rather than to empty, because
    * a restore with no state is a form the browser has nothing recorded for,
    * which is the same situation as a fresh one.
+   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
+   * not. The control shows no message for it: `reportValidity()` does that.
+   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
+   * form's `checkValidity()`, as connecting does for the form it starts in.
    * - `formDisabledCallback(disabled: boolean) => void`: Called by the browser when an ancestor fieldset is disabled or enabled.
    *
    * **The argument is the effective state, and taking it whole is what latched
@@ -92604,15 +92616,11 @@ export type CustomElementsSolidJs = {
    * the fieldset's hold is not recorded. There is no callback to learn it from
    * and reading `:disabled` here would answer about the attribute we are in the
    * middle of removing.
-   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
-   * not. The control shows no message for it: `reportValidity()` does that.
    * - `reportValidity() => boolean`: Returns whether the control is valid, and when it is not, fires `invalid`
    * and shows the browser's message at the control.
    * - `setCustomValidity(message: string) => void`: Marks the control invalid with `message`, or clears that with an empty
    * string, as on a native control. The form does not submit while it is set.
    * - `focus(options?: FocusOptions) => void`: Moves focus to the control, as focusing a native control does.
-   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
-   * form's `checkValidity()`, as connecting does for the form it starts in.
    *
    * ## CSS Custom Properties
    *
@@ -94209,6 +94217,10 @@ export type CustomElementsSolidJs = {
    * a restore with no state is a form the browser has nothing recorded for,
    * which is the same situation as a fresh one.
    * - `focus(options?: FocusOptions) => void`: Moves focus to the control, as focusing a native control does.
+   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
+   * not. The control shows no message for it: `reportValidity()` does that.
+   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
+   * form's `checkValidity()`, as connecting does for the form it starts in.
    * - `formDisabledCallback(disabled: boolean) => void`: Called by the browser when an ancestor fieldset is disabled or enabled.
    *
    * **The argument is the effective state, and taking it whole is what latched
@@ -94242,14 +94254,10 @@ export type CustomElementsSolidJs = {
    * the fieldset's hold is not recorded. There is no callback to learn it from
    * and reading `:disabled` here would answer about the attribute we are in the
    * middle of removing.
-   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
-   * not. The control shows no message for it: `reportValidity()` does that.
    * - `reportValidity() => boolean`: Returns whether the control is valid, and when it is not, fires `invalid`
    * and shows the browser's message at the control.
    * - `setCustomValidity(message: string) => void`: Marks the control invalid with `message`, or clears that with an empty
    * string, as on a native control. The form does not submit while it is set.
-   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
-   * form's `checkValidity()`, as connecting does for the form it starts in.
    *
    * ## CSS Custom Properties
    *
@@ -94719,6 +94727,10 @@ export type CustomElementsSolidJs = {
    * Falling back to what the markup declared rather than to empty, because
    * a restore with no state is a form the browser has nothing recorded for,
    * which is the same situation as a fresh one.
+   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
+   * not. The control shows no message for it: `reportValidity()` does that.
+   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
+   * form's `checkValidity()`, as connecting does for the form it starts in.
    * - `formDisabledCallback(disabled: boolean) => void`: Called by the browser when an ancestor fieldset is disabled or enabled.
    *
    * **The argument is the effective state, and taking it whole is what latched
@@ -94752,15 +94764,11 @@ export type CustomElementsSolidJs = {
    * the fieldset's hold is not recorded. There is no callback to learn it from
    * and reading `:disabled` here would answer about the attribute we are in the
    * middle of removing.
-   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
-   * not. The control shows no message for it: `reportValidity()` does that.
    * - `reportValidity() => boolean`: Returns whether the control is valid, and when it is not, fires `invalid`
    * and shows the browser's message at the control.
    * - `setCustomValidity(message: string) => void`: Marks the control invalid with `message`, or clears that with an empty
    * string, as on a native control. The form does not submit while it is set.
    * - `focus(options?: FocusOptions) => void`: Moves focus to the control, as focusing a native control does.
-   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
-   * form's `checkValidity()`, as connecting does for the form it starts in.
    *
    * ## CSS Custom Properties
    *
@@ -96483,6 +96491,10 @@ export type CustomElementsSolidJs = {
    * - `click() => void`: Turns the switch on or off, as `click()` does a native checkbox: passed to the control
    * inside, so the one click a listener hears is the control's, after it has
    * moved. See `HostClickController`.
+   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
+   * not. The control shows no message for it: `reportValidity()` does that.
+   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
+   * form's `checkValidity()`, as connecting does for the form it starts in.
    * - `formDisabledCallback(disabled: boolean) => void`: Called by the browser when an ancestor fieldset is disabled or enabled.
    *
    * **The argument is the effective state, and taking it whole is what latched
@@ -96516,15 +96528,11 @@ export type CustomElementsSolidJs = {
    * the fieldset's hold is not recorded. There is no callback to learn it from
    * and reading `:disabled` here would answer about the attribute we are in the
    * middle of removing.
-   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
-   * not. The control shows no message for it: `reportValidity()` does that.
    * - `reportValidity() => boolean`: Returns whether the control is valid, and when it is not, fires `invalid`
    * and shows the browser's message at the control.
    * - `setCustomValidity(message: string) => void`: Marks the control invalid with `message`, or clears that with an empty
    * string, as on a native control. The form does not submit while it is set.
    * - `focus(options?: FocusOptions) => void`: Moves focus to the control, as focusing a native control does.
-   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
-   * form's `checkValidity()`, as connecting does for the form it starts in.
    *
    * ## CSS Custom Properties
    *
@@ -98139,6 +98147,10 @@ export type CustomElementsSolidJs = {
    * selected after. It sends no event, as the native method sends none.
    * - `select() => void`: Selects everything in the field.
    * - `focus(options?: FocusOptions) => void`: Moves focus to the control, as focusing a native control does.
+   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
+   * not. The control shows no message for it: `reportValidity()` does that.
+   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
+   * form's `checkValidity()`, as connecting does for the form it starts in.
    * - `formDisabledCallback(disabled: boolean) => void`: Called by the browser when an ancestor fieldset is disabled or enabled.
    *
    * **The argument is the effective state, and taking it whole is what latched
@@ -98172,14 +98184,10 @@ export type CustomElementsSolidJs = {
    * the fieldset's hold is not recorded. There is no callback to learn it from
    * and reading `:disabled` here would answer about the attribute we are in the
    * middle of removing.
-   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
-   * not. The control shows no message for it: `reportValidity()` does that.
    * - `reportValidity() => boolean`: Returns whether the control is valid, and when it is not, fires `invalid`
    * and shows the browser's message at the control.
    * - `setCustomValidity(message: string) => void`: Marks the control invalid with `message`, or clears that with an empty
    * string, as on a native control. The form does not submit while it is set.
-   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
-   * form's `checkValidity()`, as connecting does for the form it starts in.
    *
    * ## CSS Custom Properties
    *
@@ -98509,6 +98517,10 @@ export type CustomElementsSolidJs = {
    * Falling back to what the markup declared rather than to empty, because
    * a restore with no state is a form the browser has nothing recorded for,
    * which is the same situation as a fresh one.
+   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
+   * not. The control shows no message for it: `reportValidity()` does that.
+   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
+   * form's `checkValidity()`, as connecting does for the form it starts in.
    * - `formDisabledCallback(disabled: boolean) => void`: Called by the browser when an ancestor fieldset is disabled or enabled.
    *
    * **The argument is the effective state, and taking it whole is what latched
@@ -98542,14 +98554,10 @@ export type CustomElementsSolidJs = {
    * the fieldset's hold is not recorded. There is no callback to learn it from
    * and reading `:disabled` here would answer about the attribute we are in the
    * middle of removing.
-   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
-   * not. The control shows no message for it: `reportValidity()` does that.
    * - `reportValidity() => boolean`: Returns whether the control is valid, and when it is not, fires `invalid`
    * and shows the browser's message at the control.
    * - `setCustomValidity(message: string) => void`: Marks the control invalid with `message`, or clears that with an empty
    * string, as on a native control. The form does not submit while it is set.
-   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
-   * form's `checkValidity()`, as connecting does for the form it starts in.
    *
    * ## CSS Custom Properties
    *
@@ -98971,6 +98979,10 @@ export type CustomElementsSolidJs = {
    * calls this again afterwards. The guard below makes the early call harmless
    * rather than wrong, which is why it can be left in.
    * - `focus(options?: FocusOptions) => void`: Moves focus to the control, as focusing a native control does.
+   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
+   * not. The control shows no message for it: `reportValidity()` does that.
+   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
+   * form's `checkValidity()`, as connecting does for the form it starts in.
    * - `formDisabledCallback(disabled: boolean) => void`: Called by the browser when an ancestor fieldset is disabled or enabled.
    *
    * **The argument is the effective state, and taking it whole is what latched
@@ -99004,14 +99016,10 @@ export type CustomElementsSolidJs = {
    * the fieldset's hold is not recorded. There is no callback to learn it from
    * and reading `:disabled` here would answer about the attribute we are in the
    * middle of removing.
-   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
-   * not. The control shows no message for it: `reportValidity()` does that.
    * - `reportValidity() => boolean`: Returns whether the control is valid, and when it is not, fires `invalid`
    * and shows the browser's message at the control.
    * - `setCustomValidity(message: string) => void`: Marks the control invalid with `message`, or clears that with an empty
    * string, as on a native control. The form does not submit while it is set.
-   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
-   * form's `checkValidity()`, as connecting does for the form it starts in.
    *
    * ## CSS Custom Properties
    *
@@ -99807,6 +99815,10 @@ export type CustomElementsSolidJs = {
    * Falling back to what the markup declared rather than to empty, because
    * a restore with no state is a form the browser has nothing recorded for,
    * which is the same situation as a fresh one.
+   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
+   * not. The control shows no message for it: `reportValidity()` does that.
+   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
+   * form's `checkValidity()`, as connecting does for the form it starts in.
    * - `formDisabledCallback(disabled: boolean) => void`: Called by the browser when an ancestor fieldset is disabled or enabled.
    *
    * **The argument is the effective state, and taking it whole is what latched
@@ -99840,15 +99852,11 @@ export type CustomElementsSolidJs = {
    * the fieldset's hold is not recorded. There is no callback to learn it from
    * and reading `:disabled` here would answer about the attribute we are in the
    * middle of removing.
-   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
-   * not. The control shows no message for it: `reportValidity()` does that.
    * - `reportValidity() => boolean`: Returns whether the control is valid, and when it is not, fires `invalid`
    * and shows the browser's message at the control.
    * - `setCustomValidity(message: string) => void`: Marks the control invalid with `message`, or clears that with an empty
    * string, as on a native control. The form does not submit while it is set.
    * - `focus(options?: FocusOptions) => void`: Moves focus to the control, as focusing a native control does.
-   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
-   * form's `checkValidity()`, as connecting does for the form it starts in.
    *
    * ## CSS Custom Properties
    *