@fusion.dev/helix-headless 0.182.0 → 0.182.2

package/types/jsx.d.ts

@@ -38868,7 +38868,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.
@@ -39610,7 +39611,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
@@ -41125,6 +41128,10 @@ export type CustomElements = {
    * a reasonable way to send.
    * - `formResetCallback() => void`: Puts back the draft the markup declared when the form is 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
@@ -41158,15 +41165,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 Parts
    *
@@ -41736,6 +41739,10 @@ export type CustomElements = {
    * they declared, and its value is read from them. A `value` the markup wrote
    * is pushed again at the next update, after the boxes have reset, and an
    * update is asked for, since an unchanged value schedules none.
+   * - `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
@@ -41769,15 +41776,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 Parts
    *
@@ -42000,6 +42003,10 @@ export type CustomElements = {
    * checked>` declares itself checked and a reset returns there, because the
    * attribute is its default. `checked` never reflects, so the attribute is
    * still what the page wrote.
+   * - `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
@@ -42033,15 +42040,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 Parts
    *
@@ -42698,6 +42701,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
@@ -42731,14 +42738,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
    *
@@ -43113,6 +43116,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
@@ -43146,14 +43153,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
    *
@@ -43564,6 +43567,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
@@ -43597,15 +43604,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 Parts
    *
@@ -44103,8 +44106,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
@@ -45093,6 +45097,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
@@ -45126,14 +45134,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 Parts
    *
@@ -45529,6 +45533,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
@@ -45562,14 +45570,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
    *
@@ -47240,6 +47244,10 @@ export type CustomElements = {
    * owes is the report to the form, and no `input` or `change`: a native file
    * input sends neither on `form.reset()`, measured in Chromium, where this
    * sent both.
+   * - `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
@@ -47273,14 +47281,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 Parts
    *
@@ -48247,6 +48251,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
@@ -48280,14 +48288,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 Parts
    *
@@ -49483,8 +49487,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
@@ -50106,6 +50111,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
@@ -50139,14 +50148,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 Parts
    *
@@ -51908,6 +51913,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
@@ -51941,15 +51950,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 Parts
    *
@@ -55018,6 +55023,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
@@ -55051,14 +55060,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 Parts
    *
@@ -56192,6 +56197,10 @@ export type CustomElements = {
    *
    * - `formResetCallback() => void`: Returns to the size the markup declared, as a native `<select>` does on a 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
@@ -56225,15 +56234,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 Parts
    *
@@ -56575,6 +56580,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
@@ -56608,14 +56617,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 Parts
    *
@@ -57431,6 +57436,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
@@ -57464,15 +57473,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 Parts
    *
@@ -57870,6 +57875,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
@@ -57903,15 +57912,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
    *
@@ -58699,6 +58704,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
@@ -58732,14 +58741,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
    *
@@ -59219,6 +59224,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
@@ -59252,15 +59261,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
    *
@@ -60778,6 +60783,10 @@ export type CustomElements = {
    * checked>` declares itself checked and a reset returns there, because the
    * attribute is its default. `checked` never reflects, so the attribute is
    * still what the page wrote.
+   * - `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
@@ -60811,15 +60820,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 Parts
    *
@@ -62510,6 +62515,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
@@ -62543,14 +62552,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 Parts
    *
@@ -62913,6 +62918,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
@@ -62946,14 +62955,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 Parts
    *
@@ -63403,6 +63408,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
@@ -63436,14 +63445,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 Parts
    *
@@ -64294,6 +64299,10 @@ export type CustomElements = {
    * Both halves are dropped, the consumer's and the control's, because a
    * reset means the form is as it was served. Clearing only the internal one
    * would leave a control that had been written to stuck at that value.
+   * - `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
@@ -64327,15 +64336,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 Parts
    *
@@ -68568,7 +68573,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.
@@ -69317,7 +69323,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
@@ -70849,6 +70857,10 @@ export type CustomElementsSolidJs = {
    * a reasonable way to send.
    * - `formResetCallback() => void`: Puts back the draft the markup declared when the form is 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
@@ -70882,15 +70894,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 Parts
    *
@@ -71465,6 +71473,10 @@ export type CustomElementsSolidJs = {
    * they declared, and its value is read from them. A `value` the markup wrote
    * is pushed again at the next update, after the boxes have reset, and an
    * update is asked for, since an unchanged value schedules none.
+   * - `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
@@ -71498,15 +71510,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 Parts
    *
@@ -71730,6 +71738,10 @@ export type CustomElementsSolidJs = {
    * checked>` declares itself checked and a reset returns there, because the
    * attribute is its default. `checked` never reflects, so the attribute is
    * still what the page wrote.
+   * - `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
@@ -71763,15 +71775,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 Parts
    *
@@ -72437,6 +72445,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
@@ -72470,14 +72482,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
    *
@@ -72853,6 +72861,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
@@ -72886,14 +72898,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
    *
@@ -73305,6 +73313,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
@@ -73338,15 +73350,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 Parts
    *
@@ -73850,8 +73858,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
@@ -74844,6 +74853,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
@@ -74877,14 +74890,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 Parts
    *
@@ -75283,6 +75292,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
@@ -75316,14 +75329,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
    *
@@ -77014,6 +77023,10 @@ export type CustomElementsSolidJs = {
    * owes is the report to the form, and no `input` or `change`: a native file
    * input sends neither on `form.reset()`, measured in Chromium, where this
    * sent both.
+   * - `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
@@ -77047,14 +77060,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 Parts
    *
@@ -78028,6 +78037,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
@@ -78061,14 +78074,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 Parts
    *
@@ -79272,8 +79281,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
@@ -79902,6 +79912,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
@@ -79935,14 +79949,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 Parts
    *
@@ -81726,6 +81736,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
@@ -81759,15 +81773,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 Parts
    *
@@ -84882,6 +84892,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
@@ -84915,14 +84929,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 Parts
    *
@@ -86067,6 +86077,10 @@ export type CustomElementsSolidJs = {
    *
    * - `formResetCallback() => void`: Returns to the size the markup declared, as a native `<select>` does on a 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
@@ -86100,15 +86114,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 Parts
    *
@@ -86452,6 +86462,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
@@ -86485,14 +86499,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 Parts
    *
@@ -87323,6 +87333,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
@@ -87356,15 +87370,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 Parts
    *
@@ -87766,6 +87776,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
@@ -87799,15 +87813,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
    *
@@ -88600,6 +88610,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
@@ -88633,14 +88647,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
    *
@@ -89129,6 +89139,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
@@ -89162,15 +89176,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
    *
@@ -90714,6 +90724,10 @@ export type CustomElementsSolidJs = {
    * checked>` declares itself checked and a reset returns there, because the
    * attribute is its default. `checked` never reflects, so the attribute is
    * still what the page wrote.
+   * - `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
@@ -90747,15 +90761,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 Parts
    *
@@ -92474,6 +92484,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
@@ -92507,14 +92521,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 Parts
    *
@@ -92880,6 +92890,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
@@ -92913,14 +92927,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 Parts
    *
@@ -93373,6 +93383,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
@@ -93406,14 +93420,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 Parts
    *
@@ -94276,6 +94286,10 @@ export type CustomElementsSolidJs = {
    * Both halves are dropped, the consumer's and the control's, because a
    * reset means the form is as it was served. Clearing only the internal one
    * would leave a control that had been written to stuck at that value.
+   * - `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
@@ -94309,15 +94323,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 Parts
    *