@fusion.dev/helix 0.182.0 → 0.182.2

package/types/jsx.d.ts

@@ -44146,7 +44146,8 @@ export type CustomElements = {
    * - `axis`: The numbers of one scale: the primary under `value-axis`, and both when `secondary` splits the chart into two scales.
    * - `band`: The category band under the pointer.
    * - `bar`: One column. Under `stacked`, one segment of a category's column.
-   * - `bar-end`: Under `stacked`, the segment at a column's far end: the last positive segment above zero and the last negative one below it. Its `data-end` is `positive` or `negative`. A blank or a zero segment is never the end. Set together with `bar`.
+   * - `bar-end`: The bar at a column's far end, the end away from zero, which is the end to round. A column standing alone is its own far end. Under `stacked`, the last positive segment above zero and the last negative one below it. Its `data-end` is `positive` or `negative`. A blank or a zero is never the end. Set together with `bar`.
+   * - `bar-end-negative`: A far end below zero, whose far end is its bottom, or its inline start when the bars run across. Set together with `bar-end`.
    * - `bar-wash-end`: The far stop of a bar's gradient, where one is used.
    * - `bar-wash-start`: The stop of a bar's gradient at its base.
    * - `baseline`: The line the columns stand on.
@@ -44877,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
@@ -46412,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
@@ -46445,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
    *
@@ -46977,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
@@ -47010,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
    *
@@ -47263,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
@@ -47296,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
    *
@@ -47916,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
@@ -47949,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
    *
@@ -48328,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
@@ -48361,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
    *
@@ -48747,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
@@ -48780,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
    *
@@ -49219,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
@@ -50103,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
@@ -50136,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
    *
@@ -50520,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
@@ -50553,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
    *
@@ -52177,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
@@ -52210,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
    *
@@ -53001,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
@@ -53034,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
    *
@@ -54396,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
@@ -55007,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
@@ -55040,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
    *
@@ -56681,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
@@ -56714,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
    *
@@ -59645,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
@@ -59678,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
    *
@@ -60895,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
@@ -60928,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
    *
@@ -61243,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
@@ -61276,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
    *
@@ -62041,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
@@ -62074,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
    *
@@ -62542,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
@@ -62575,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
    *
@@ -64153,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
@@ -64186,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
    *
@@ -64654,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
@@ -64687,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
    *
@@ -66382,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
@@ -66415,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
    *
@@ -68007,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
@@ -68040,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
    *
@@ -68374,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
@@ -68407,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
    *
@@ -68833,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
@@ -68866,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
    *
@@ -69649,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
@@ -69682,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
    *
@@ -73881,7 +73886,8 @@ export type CustomElementsSolidJs = {
    * - `axis`: The numbers of one scale: the primary under `value-axis`, and both when `secondary` splits the chart into two scales.
    * - `band`: The category band under the pointer.
    * - `bar`: One column. Under `stacked`, one segment of a category's column.
-   * - `bar-end`: Under `stacked`, the segment at a column's far end: the last positive segment above zero and the last negative one below it. Its `data-end` is `positive` or `negative`. A blank or a zero segment is never the end. Set together with `bar`.
+   * - `bar-end`: The bar at a column's far end, the end away from zero, which is the end to round. A column standing alone is its own far end. Under `stacked`, the last positive segment above zero and the last negative one below it. Its `data-end` is `positive` or `negative`. A blank or a zero is never the end. Set together with `bar`.
+   * - `bar-end-negative`: A far end below zero, whose far end is its bottom, or its inline start when the bars run across. Set together with `bar-end`.
    * - `bar-wash-end`: The far stop of a bar's gradient, where one is used.
    * - `bar-wash-start`: The stop of a bar's gradient at its base.
    * - `baseline`: The line the columns stand on.
@@ -74627,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
@@ -76182,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
@@ -76215,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
    *
@@ -76755,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
@@ -76788,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
    *
@@ -77044,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
@@ -77077,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
    *
@@ -77705,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
@@ -77738,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
    *
@@ -78120,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
@@ -78153,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
    *
@@ -78542,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
@@ -78575,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
    *
@@ -79020,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
@@ -79910,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
@@ -79943,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
    *
@@ -80330,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
@@ -80363,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
    *
@@ -82017,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
@@ -82050,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
    *
@@ -82856,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
@@ -82889,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
    *
@@ -84269,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
@@ -84890,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
@@ -84923,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
    *
@@ -86588,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
@@ -86621,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
    *
@@ -89618,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
@@ -89651,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
    *
@@ -90891,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
@@ -90924,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
    *
@@ -91245,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
@@ -91278,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
    *
@@ -92060,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
@@ -92093,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
    *
@@ -92569,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
@@ -92602,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
    *
@@ -94207,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
@@ -94240,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
    *
@@ -94717,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
@@ -94750,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
    *
@@ -96481,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
@@ -96514,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
    *
@@ -98137,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
@@ -98170,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
    *
@@ -98507,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
@@ -98540,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
    *
@@ -98969,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
@@ -99002,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
    *
@@ -99805,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
@@ -99838,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
    *