@fusion.dev/helix-headless 0.182.1 → 0.183.0

package/types/jsx.d.ts

@@ -36982,6 +36982,13 @@ are rendered at a time.
 An `aria-label` or `aria-labelledby` on the host names the list too, and
 wins over this. */
   label?: (HelixHeadlessVirtualList["label"]) | undefined;
+  /** How items of more than one column are laid out. `grid`, the default, puts
+them in lines of equal columns. `waterfall` puts each item, in the order
+of the set, under the column that ends highest, as a wall of photos of
+different heights is: `columns`, or `min-column-width`, says how many
+columns. Rows of a waterfall are measured, and Up and Down move along a
+column. */
+  layout?: (HelixHeadlessVirtualList["layout"]) | undefined;
   /** Marks the list as busy fetching more items, and draws a row after the last
 item that says so.
 
@@ -37014,14 +37021,15 @@ follows the box as it resizes, which `columns` then does not decide. */
   /** Which way the list runs. `horizontal` lays the items out along a line
 and scrolls it sideways: Left and Right move between items, the other
 way round on a right-to-left page, and `estimate` is an item's width. A
-grid always runs down. */
+grid and a waterfall always run down. */
   orientation?: (HelixHeadlessVirtualList["orientation"]) | undefined;
   /** Lets a reader move items, once `@fusion.dev/helix/virtual-list/reorder`
 (or `@fusion.dev/helix-headless/virtual-list/reorder`) is imported: Alt
 with an arrow moves the row the keys are on, and a pointer drags a row.
 The list moves no item itself: you move your `items` on `helix-reorder`.
 Without that import it does nothing, so a list that never moves items
-carries none of the code. A list of one column, without sections. */
+carries none of the code. A list of one column, without sections or a
+waterfall. */
   reorderable?: (HelixHeadlessVirtualList["reorderable"]) | undefined;
   /** The field of each item that names its section, as a key or a path of
 keys. Set, the items are drawn in sections: a header, then the items, in
@@ -37150,6 +37158,13 @@ are rendered at a time.
 An `aria-label` or `aria-labelledby` on the host names the list too, and
 wins over this. */
   "prop:label"?: (HelixHeadlessVirtualList["label"]) | undefined;
+  /** How items of more than one column are laid out. `grid`, the default, puts
+them in lines of equal columns. `waterfall` puts each item, in the order
+of the set, under the column that ends highest, as a wall of photos of
+different heights is: `columns`, or `min-column-width`, says how many
+columns. Rows of a waterfall are measured, and Up and Down move along a
+column. */
+  "prop:layout"?: (HelixHeadlessVirtualList["layout"]) | undefined;
   /** Marks the list as busy fetching more items, and draws a row after the last
 item that says so.
 
@@ -37182,14 +37197,15 @@ follows the box as it resizes, which `columns` then does not decide. */
   /** Which way the list runs. `horizontal` lays the items out along a line
 and scrolls it sideways: Left and Right move between items, the other
 way round on a right-to-left page, and `estimate` is an item's width. A
-grid always runs down. */
+grid and a waterfall always run down. */
   "prop:orientation"?: (HelixHeadlessVirtualList["orientation"]) | undefined;
   /** Lets a reader move items, once `@fusion.dev/helix/virtual-list/reorder`
 (or `@fusion.dev/helix-headless/virtual-list/reorder`) is imported: Alt
 with an arrow moves the row the keys are on, and a pointer drags a row.
 The list moves no item itself: you move your `items` on `helix-reorder`.
 Without that import it does nothing, so a list that never moves items
-carries none of the code. A list of one column, without sections. */
+carries none of the code. A list of one column, without sections or a
+waterfall. */
   "prop:reorderable"?: (HelixHeadlessVirtualList["reorderable"]) | undefined;
   /** The field of each item that names its section, as a key or a path of
 keys. Set, the items are drawn in sections: a header, then the items, in
@@ -38870,6 +38886,7 @@ export type CustomElements = {
    * - `bar`: One column. Under `stacked`, one segment of a category's column.
    * - `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-negative`: A bar below zero, standing alone or any segment of a stack below it, whose base is its top, or its inline end when the bars run across. Set together with `bar`.
    * - `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.
@@ -39611,7 +39628,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
@@ -41126,6 +41145,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
@@ -41159,15 +41182,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
    *
@@ -41737,6 +41756,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
@@ -41770,15 +41793,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
    *
@@ -42001,6 +42020,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
@@ -42034,15 +42057,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
    *
@@ -42699,6 +42718,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
@@ -42732,14 +42755,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
    *
@@ -43114,6 +43133,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
@@ -43147,14 +43170,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
    *
@@ -43565,6 +43584,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
@@ -43598,15 +43621,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
    *
@@ -44104,8 +44123,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
@@ -45094,6 +45114,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
@@ -45127,14 +45151,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
    *
@@ -45530,6 +45550,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
@@ -45563,14 +45587,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
    *
@@ -47241,6 +47261,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
@@ -47274,14 +47298,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
    *
@@ -48248,6 +48268,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
@@ -48281,14 +48305,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
    *
@@ -49484,8 +49504,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
@@ -50107,6 +50128,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
@@ -50140,14 +50165,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
    *
@@ -51909,6 +51930,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
@@ -51942,15 +51967,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
    *
@@ -55019,6 +55040,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
@@ -55052,14 +55077,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
    *
@@ -56193,6 +56214,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
@@ -56226,15 +56251,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
    *
@@ -56576,6 +56597,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
@@ -56609,14 +56634,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
    *
@@ -57432,6 +57453,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
@@ -57465,15 +57490,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
    *
@@ -57871,6 +57892,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
@@ -57904,15 +57929,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
    *
@@ -58700,6 +58721,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
@@ -58733,14 +58758,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
    *
@@ -59220,6 +59241,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
@@ -59253,15 +59278,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
    *
@@ -60779,6 +60800,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
@@ -60812,15 +60837,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
    *
@@ -62511,6 +62532,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
@@ -62544,14 +62569,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
    *
@@ -62914,6 +62935,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
@@ -62947,14 +62972,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
    *
@@ -63404,6 +63425,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
@@ -63437,14 +63462,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
    *
@@ -64295,6 +64316,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
@@ -64328,15 +64353,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
    *
@@ -66676,6 +66697,32 @@ export type CustomElements = {
    * smallest item size, and follows the box as it resizes. `gap` spaces the rows, and the columns
    * of a grid, by a number of pixels the list counts in each row's place.
    *
+   * A grid without `selection-mode` is a grid to a reader, as the APG's grid
+   * and React Aria's grid list are: the box is a `grid` with `aria-rowcount`
+   * and `aria-colcount`, each line drawn is a `row` with `aria-rowindex`, and
+   * each item a `gridcell` with `aria-colindex`. Each line is a slot of the
+   * list's own, so your rows stay its children: give an item one element. With
+   * `selection-mode` it stays a list box of options, as React Aria's list box
+   * in a grid layout does.
+   *
+   * **A waterfall.** `layout="waterfall"` puts each item, in the order of the
+   * set, under the column that ends highest so far, the leftmost of a tie, as a
+   * wall of photos of different heights is, and as React Aria's waterfall
+   * layout and TanStack Virtual's lanes do. `columns`, or `min-column-width`,
+   * says how many columns. Every item is measured, at the width of its column,
+   * and placed at its column and its height, so items of any height leave no
+   * holes. The list draws the items that reach into the box, and the item
+   * holding focus. A reader hears a list, or a list box, in the order of the
+   * set, which is also the order Tab and a screen reader's own keys take.
+   *
+   * In a waterfall, Down and Up move along the column to the next or the
+   * previous item in it, Right and Left move to the next or the previous
+   * column, to the item there that sits beside this one the most, or the
+   * nearest above where none does, and Page Down and Page Up move a box down
+   * or up the column. Home and End go to the first and the last item of the
+   * set, and Shift with a key takes in the items between in the order of the
+   * set.
+   *
    * **Across.** `orientation="horizontal"` lays the items out along a line and
    * scrolls it sideways, as a strip of cards does, windowed the same way:
    * `estimate` is then an item's width, and the box needs an inline size.
@@ -66694,10 +66741,11 @@ export type CustomElements = {
    *
    * | Key | What it does |
    * |---|---|
-   * | Down, Up | Moves to the next or the previous item, or in a grid to the item in the same column on the next or the previous line. |
-   * | Right, Left | In a grid, moves to the next or the previous item along the line, the other way round on a right-to-left page. In a list that runs across, moves to the next or the previous item the same way, and Down and Up are left to the row. |
-   * | Home, End | Moves to the first or the last item. |
-   * | Page Down, Page Up | Moves by the number of items, or of lines in a grid, on screen. |
+   * | Down, Up | Moves to the next or the previous item, or in a grid to the item in the same column on the next or the previous line, or in a waterfall to the next or the previous item down the same column. |
+   * | Right, Left | In a grid, moves to the next or the previous item along the line, the other way round on a right-to-left page. In a waterfall, moves to the item beside in the next or the previous column. In a list that runs across, moves to the next or the previous item the same way, and Down and Up are left to the row. |
+   * | Home, End | Moves to the first or the last item. In a grid without `selection-mode`, to the first or the last item of the line. |
+   * | Control or Command with Home or End | In a grid without `selection-mode`, moves to the first or the last item. |
+   * | Page Down, Page Up | Moves by the number of items, or of lines in a grid, on screen, or in a waterfall a box down or up the column. |
    * | A letter or a word | Moves to the next item whose text starts with what you typed. |
    * | Escape | Lets go of every chosen item, in a list with `selection-mode`. |
    * | Alt with Up or Down | In a `reorderable` list, moves the item a place. Alt with Home or End moves it to either end. |
@@ -66712,8 +66760,9 @@ export type CustomElements = {
    * or the item itself when it is a string or a number.
    *
    * Each row says its place in the whole set with `aria-posinset` and
-   * `aria-setsize`, so a screen reader says "4,000 of 10,000". The row holding
-   * focus stays drawn when it scrolls out.
+   * `aria-setsize`, so a screen reader says "4,000 of 10,000", and each cell of
+   * a grid its line and its column. The row holding focus stays drawn when it
+   * scrolls out.
    *
    * **Selecting.** `selection-mode` makes the list a list box a reader chooses
    * from: `single` selects one item and `multiple` any number. Space or a press
@@ -66821,6 +66870,12 @@ export type CustomElements = {
    *
    * An `aria-label` or `aria-labelledby` on the host names the list too, and
    * wins over this.
+   * - `layout`: How items of more than one column are laid out. `grid`, the default, puts
+   * them in lines of equal columns. `waterfall` puts each item, in the order
+   * of the set, under the column that ends highest, as a wall of photos of
+   * different heights is: `columns`, or `min-column-width`, says how many
+   * columns. Rows of a waterfall are measured, and Up and Down move along a
+   * column.
    * - `loading`: Marks the list as busy fetching more items, and draws a row after the last
    * item that says so.
    *
@@ -66843,13 +66898,14 @@ export type CustomElements = {
    * - `orientation`: Which way the list runs. `horizontal` lays the items out along a line
    * and scrolls it sideways: Left and Right move between items, the other
    * way round on a right-to-left page, and `estimate` is an item's width. A
-   * grid always runs down.
+   * grid and a waterfall always run down.
    * - `reorderable`: Lets a reader move items, once `@fusion.dev/helix/virtual-list/reorder`
    * (or `@fusion.dev/helix-headless/virtual-list/reorder`) is imported: Alt
    * with an arrow moves the row the keys are on, and a pointer drags a row.
    * The list moves no item itself: you move your `items` on `helix-reorder`.
    * Without that import it does nothing, so a list that never moves items
-   * carries none of the code. A list of one column, without sections.
+   * carries none of the code. A list of one column, without sections or a
+   * waterfall.
    * - `section-field`/`sectionField`: The field of each item that names its section, as a key or a path of
    * keys. Set, the items are drawn in sections: a header, then the items, in
    * an element with the `group` role that the header names. A section starts
@@ -68571,6 +68627,7 @@ export type CustomElementsSolidJs = {
    * - `bar`: One column. Under `stacked`, one segment of a category's column.
    * - `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-negative`: A bar below zero, standing alone or any segment of a stack below it, whose base is its top, or its inline end when the bars run across. Set together with `bar`.
    * - `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.
@@ -69319,7 +69376,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
@@ -70851,6 +70910,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
@@ -70884,15 +70947,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
    *
@@ -71467,6 +71526,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
@@ -71500,15 +71563,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
    *
@@ -71732,6 +71791,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
@@ -71765,15 +71828,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
    *
@@ -72439,6 +72498,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
@@ -72472,14 +72535,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
    *
@@ -72855,6 +72914,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
@@ -72888,14 +72951,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
    *
@@ -73307,6 +73366,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
@@ -73340,15 +73403,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
    *
@@ -73852,8 +73911,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
@@ -74846,6 +74906,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
@@ -74879,14 +74943,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
    *
@@ -75285,6 +75345,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
@@ -75318,14 +75382,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
    *
@@ -77016,6 +77076,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
@@ -77049,14 +77113,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
    *
@@ -78030,6 +78090,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
@@ -78063,14 +78127,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
    *
@@ -79274,8 +79334,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
@@ -79904,6 +79965,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
@@ -79937,14 +80002,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
    *
@@ -81728,6 +81789,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
@@ -81761,15 +81826,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
    *
@@ -84884,6 +84945,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
@@ -84917,14 +84982,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
    *
@@ -86069,6 +86130,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
@@ -86102,15 +86167,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
    *
@@ -86454,6 +86515,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
@@ -86487,14 +86552,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
    *
@@ -87325,6 +87386,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
@@ -87358,15 +87423,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
    *
@@ -87768,6 +87829,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
@@ -87801,15 +87866,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
    *
@@ -88602,6 +88663,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
@@ -88635,14 +88700,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
    *
@@ -89131,6 +89192,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
@@ -89164,15 +89229,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
    *
@@ -90716,6 +90777,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
@@ -90749,15 +90814,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
    *
@@ -92476,6 +92537,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
@@ -92509,14 +92574,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
    *
@@ -92882,6 +92943,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
@@ -92915,14 +92980,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
    *
@@ -93375,6 +93436,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
@@ -93408,14 +93473,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
    *
@@ -94278,6 +94339,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
@@ -94311,15 +94376,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
    *
@@ -96690,6 +96751,32 @@ export type CustomElementsSolidJs = {
    * smallest item size, and follows the box as it resizes. `gap` spaces the rows, and the columns
    * of a grid, by a number of pixels the list counts in each row's place.
    *
+   * A grid without `selection-mode` is a grid to a reader, as the APG's grid
+   * and React Aria's grid list are: the box is a `grid` with `aria-rowcount`
+   * and `aria-colcount`, each line drawn is a `row` with `aria-rowindex`, and
+   * each item a `gridcell` with `aria-colindex`. Each line is a slot of the
+   * list's own, so your rows stay its children: give an item one element. With
+   * `selection-mode` it stays a list box of options, as React Aria's list box
+   * in a grid layout does.
+   *
+   * **A waterfall.** `layout="waterfall"` puts each item, in the order of the
+   * set, under the column that ends highest so far, the leftmost of a tie, as a
+   * wall of photos of different heights is, and as React Aria's waterfall
+   * layout and TanStack Virtual's lanes do. `columns`, or `min-column-width`,
+   * says how many columns. Every item is measured, at the width of its column,
+   * and placed at its column and its height, so items of any height leave no
+   * holes. The list draws the items that reach into the box, and the item
+   * holding focus. A reader hears a list, or a list box, in the order of the
+   * set, which is also the order Tab and a screen reader's own keys take.
+   *
+   * In a waterfall, Down and Up move along the column to the next or the
+   * previous item in it, Right and Left move to the next or the previous
+   * column, to the item there that sits beside this one the most, or the
+   * nearest above where none does, and Page Down and Page Up move a box down
+   * or up the column. Home and End go to the first and the last item of the
+   * set, and Shift with a key takes in the items between in the order of the
+   * set.
+   *
    * **Across.** `orientation="horizontal"` lays the items out along a line and
    * scrolls it sideways, as a strip of cards does, windowed the same way:
    * `estimate` is then an item's width, and the box needs an inline size.
@@ -96708,10 +96795,11 @@ export type CustomElementsSolidJs = {
    *
    * | Key | What it does |
    * |---|---|
-   * | Down, Up | Moves to the next or the previous item, or in a grid to the item in the same column on the next or the previous line. |
-   * | Right, Left | In a grid, moves to the next or the previous item along the line, the other way round on a right-to-left page. In a list that runs across, moves to the next or the previous item the same way, and Down and Up are left to the row. |
-   * | Home, End | Moves to the first or the last item. |
-   * | Page Down, Page Up | Moves by the number of items, or of lines in a grid, on screen. |
+   * | Down, Up | Moves to the next or the previous item, or in a grid to the item in the same column on the next or the previous line, or in a waterfall to the next or the previous item down the same column. |
+   * | Right, Left | In a grid, moves to the next or the previous item along the line, the other way round on a right-to-left page. In a waterfall, moves to the item beside in the next or the previous column. In a list that runs across, moves to the next or the previous item the same way, and Down and Up are left to the row. |
+   * | Home, End | Moves to the first or the last item. In a grid without `selection-mode`, to the first or the last item of the line. |
+   * | Control or Command with Home or End | In a grid without `selection-mode`, moves to the first or the last item. |
+   * | Page Down, Page Up | Moves by the number of items, or of lines in a grid, on screen, or in a waterfall a box down or up the column. |
    * | A letter or a word | Moves to the next item whose text starts with what you typed. |
    * | Escape | Lets go of every chosen item, in a list with `selection-mode`. |
    * | Alt with Up or Down | In a `reorderable` list, moves the item a place. Alt with Home or End moves it to either end. |
@@ -96726,8 +96814,9 @@ export type CustomElementsSolidJs = {
    * or the item itself when it is a string or a number.
    *
    * Each row says its place in the whole set with `aria-posinset` and
-   * `aria-setsize`, so a screen reader says "4,000 of 10,000". The row holding
-   * focus stays drawn when it scrolls out.
+   * `aria-setsize`, so a screen reader says "4,000 of 10,000", and each cell of
+   * a grid its line and its column. The row holding focus stays drawn when it
+   * scrolls out.
    *
    * **Selecting.** `selection-mode` makes the list a list box a reader chooses
    * from: `single` selects one item and `multiple` any number. Space or a press
@@ -96835,6 +96924,12 @@ export type CustomElementsSolidJs = {
    *
    * An `aria-label` or `aria-labelledby` on the host names the list too, and
    * wins over this.
+   * - `layout`: How items of more than one column are laid out. `grid`, the default, puts
+   * them in lines of equal columns. `waterfall` puts each item, in the order
+   * of the set, under the column that ends highest, as a wall of photos of
+   * different heights is: `columns`, or `min-column-width`, says how many
+   * columns. Rows of a waterfall are measured, and Up and Down move along a
+   * column.
    * - `loading`: Marks the list as busy fetching more items, and draws a row after the last
    * item that says so.
    *
@@ -96857,13 +96952,14 @@ export type CustomElementsSolidJs = {
    * - `orientation`: Which way the list runs. `horizontal` lays the items out along a line
    * and scrolls it sideways: Left and Right move between items, the other
    * way round on a right-to-left page, and `estimate` is an item's width. A
-   * grid always runs down.
+   * grid and a waterfall always run down.
    * - `reorderable`: Lets a reader move items, once `@fusion.dev/helix/virtual-list/reorder`
    * (or `@fusion.dev/helix-headless/virtual-list/reorder`) is imported: Alt
    * with an arrow moves the row the keys are on, and a pointer drags a row.
    * The list moves no item itself: you move your `items` on `helix-reorder`.
    * Without that import it does nothing, so a list that never moves items
-   * carries none of the code. A list of one column, without sections.
+   * carries none of the code. A list of one column, without sections or a
+   * waterfall.
    * - `section-field`/`sectionField`: The field of each item that names its section, as a key or a path of
    * keys. Set, the items are drawn in sections: a header, then the items, in
    * an element with the `group` role that the header names. A section starts