@fusion.dev/helix 0.182.1 → 0.183.0

package/types/jsx.d.ts

@@ -42018,6 +42018,13 @@ are rendered at a time.
 An `aria-label` or `aria-labelledby` on the host names the list too, and
 wins over this. */
   label?: (HelixVirtualList["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?: (HelixVirtualList["layout"]) | undefined;
   /** Marks the list as busy fetching more items, and draws a row after the last
 item that says so.
 
@@ -42050,14 +42057,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?: (HelixVirtualList["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?: (HelixVirtualList["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
@@ -42182,6 +42190,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"?: (HelixVirtualList["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"?: (HelixVirtualList["layout"]) | undefined;
   /** Marks the list as busy fetching more items, and draws a row after the last
 item that says so.
 
@@ -42214,14 +42229,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"?: (HelixVirtualList["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"?: (HelixVirtualList["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
@@ -44148,6 +44164,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.
@@ -44878,7 +44895,9 @@ export type CustomElements = {
    * submitted nothing and sent no `helix-press`. The control's own click reaches
    * the host's listeners once, retargeted, as one from a native button does. A
    * disabled button does nothing, and a pending one refuses the press.
-   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the button's form changes.
+   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the button's form changes. Its own rather than
+   * an override: the base a button extends watches no form's checks, because
+   * a button reports no verdict of its own.
    * - `formDisabledCallback(disabled: boolean) => void`: Called by the browser when an ancestor fieldset is disabled or enabled.
    *
    * **The argument is the effective state, and taking it whole is what latched
@@ -46413,6 +46432,10 @@ export type CustomElements = {
    * forgetting of a reader's past attempt, whose message otherwise showed over
    * the emptied control the moment the form was reset.
    * - `formStateRestoreCallback(state: string | File | FormData | null) => void`: Brings back the draft when the browser restores the form.
+   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
+   * not. The control shows no message for it: `reportValidity()` does that.
+   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
+   * form's `checkValidity()`, as connecting does for the form it starts in.
    * - `formDisabledCallback(disabled: boolean) => void`: Called by the browser when an ancestor fieldset is disabled or enabled.
    *
    * **The argument is the effective state, and taking it whole is what latched
@@ -46446,15 +46469,11 @@ export type CustomElements = {
    * the fieldset's hold is not recorded. There is no callback to learn it from
    * and reading `:disabled` here would answer about the attribute we are in the
    * middle of removing.
-   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
-   * not. The control shows no message for it: `reportValidity()` does that.
    * - `reportValidity() => boolean`: Returns whether the control is valid, and when it is not, fires `invalid`
    * and shows the browser's message at the control.
    * - `setCustomValidity(message: string) => void`: Marks the control invalid with `message`, or clears that with an empty
    * string, as on a native control. The form does not submit while it is set.
    * - `focus(options?: FocusOptions) => void`: Moves focus to the control, as focusing a native control does.
-   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
-   * form's `checkValidity()`, as connecting does for the form it starts in.
    *
    * ## CSS Custom Properties
    *
@@ -46978,6 +46997,10 @@ export type CustomElements = {
    *
    * Through the base's prototype rather than `super`, because the base this
    * grafts onto is any element and only a form element has the hook.
+   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
+   * not. The control shows no message for it: `reportValidity()` does that.
+   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
+   * form's `checkValidity()`, as connecting does for the form it starts in.
    * - `formDisabledCallback(disabled: boolean) => void`: Called by the browser when an ancestor fieldset is disabled or enabled.
    *
    * **The argument is the effective state, and taking it whole is what latched
@@ -47011,15 +47034,11 @@ export type CustomElements = {
    * the fieldset's hold is not recorded. There is no callback to learn it from
    * and reading `:disabled` here would answer about the attribute we are in the
    * middle of removing.
-   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
-   * not. The control shows no message for it: `reportValidity()` does that.
    * - `reportValidity() => boolean`: Returns whether the control is valid, and when it is not, fires `invalid`
    * and shows the browser's message at the control.
    * - `setCustomValidity(message: string) => void`: Marks the control invalid with `message`, or clears that with an empty
    * string, as on a native control. The form does not submit while it is set.
    * - `focus(options?: FocusOptions) => void`: Moves focus to the control, as focusing a native control does.
-   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
-   * form's `checkValidity()`, as connecting does for the form it starts in.
    *
    * ## CSS Custom Properties
    *
@@ -47264,6 +47283,10 @@ export type CustomElements = {
    * - `click() => void`: Ticks or clears the box, as `click()` does a native checkbox: passed to the control
    * inside, so the one click a listener hears is the control's, after it has
    * moved. See `HostClickController`.
+   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
+   * not. The control shows no message for it: `reportValidity()` does that.
+   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
+   * form's `checkValidity()`, as connecting does for the form it starts in.
    * - `formDisabledCallback(disabled: boolean) => void`: Called by the browser when an ancestor fieldset is disabled or enabled.
    *
    * **The argument is the effective state, and taking it whole is what latched
@@ -47297,15 +47320,11 @@ export type CustomElements = {
    * the fieldset's hold is not recorded. There is no callback to learn it from
    * and reading `:disabled` here would answer about the attribute we are in the
    * middle of removing.
-   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
-   * not. The control shows no message for it: `reportValidity()` does that.
    * - `reportValidity() => boolean`: Returns whether the control is valid, and when it is not, fires `invalid`
    * and shows the browser's message at the control.
    * - `setCustomValidity(message: string) => void`: Marks the control invalid with `message`, or clears that with an empty
    * string, as on a native control. The form does not submit while it is set.
    * - `focus(options?: FocusOptions) => void`: Moves focus to the control, as focusing a native control does.
-   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
-   * form's `checkValidity()`, as connecting does for the form it starts in.
    *
    * ## CSS Custom Properties
    *
@@ -47917,6 +47936,10 @@ export type CustomElements = {
    * Falling back to what the markup declared rather than to empty, because
    * a restore with no state is a form the browser has nothing recorded for,
    * which is the same situation as a fresh one.
+   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
+   * not. The control shows no message for it: `reportValidity()` does that.
+   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
+   * form's `checkValidity()`, as connecting does for the form it starts in.
    * - `formDisabledCallback(disabled: boolean) => void`: Called by the browser when an ancestor fieldset is disabled or enabled.
    *
    * **The argument is the effective state, and taking it whole is what latched
@@ -47950,14 +47973,10 @@ export type CustomElements = {
    * the fieldset's hold is not recorded. There is no callback to learn it from
    * and reading `:disabled` here would answer about the attribute we are in the
    * middle of removing.
-   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
-   * not. The control shows no message for it: `reportValidity()` does that.
    * - `reportValidity() => boolean`: Returns whether the control is valid, and when it is not, fires `invalid`
    * and shows the browser's message at the control.
    * - `setCustomValidity(message: string) => void`: Marks the control invalid with `message`, or clears that with an empty
    * string, as on a native control. The form does not submit while it is set.
-   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
-   * form's `checkValidity()`, as connecting does for the form it starts in.
    *
    * ## CSS Custom Properties
    *
@@ -48329,6 +48348,10 @@ export type CustomElements = {
    * a restore with no state is a form the browser has nothing recorded for,
    * which is the same situation as a fresh one.
    * - `focus(options?: FocusOptions) => void`: Moves focus to the control, as focusing a native control does.
+   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
+   * not. The control shows no message for it: `reportValidity()` does that.
+   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
+   * form's `checkValidity()`, as connecting does for the form it starts in.
    * - `formDisabledCallback(disabled: boolean) => void`: Called by the browser when an ancestor fieldset is disabled or enabled.
    *
    * **The argument is the effective state, and taking it whole is what latched
@@ -48362,14 +48385,10 @@ export type CustomElements = {
    * the fieldset's hold is not recorded. There is no callback to learn it from
    * and reading `:disabled` here would answer about the attribute we are in the
    * middle of removing.
-   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
-   * not. The control shows no message for it: `reportValidity()` does that.
    * - `reportValidity() => boolean`: Returns whether the control is valid, and when it is not, fires `invalid`
    * and shows the browser's message at the control.
    * - `setCustomValidity(message: string) => void`: Marks the control invalid with `message`, or clears that with an empty
    * string, as on a native control. The form does not submit while it is set.
-   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
-   * form's `checkValidity()`, as connecting does for the form it starts in.
    *
    * ## CSS Custom Properties
    *
@@ -48748,6 +48767,10 @@ export type CustomElements = {
    * Falling back to what the markup declared rather than to empty, because
    * a restore with no state is a form the browser has nothing recorded for,
    * which is the same situation as a fresh one.
+   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
+   * not. The control shows no message for it: `reportValidity()` does that.
+   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
+   * form's `checkValidity()`, as connecting does for the form it starts in.
    * - `formDisabledCallback(disabled: boolean) => void`: Called by the browser when an ancestor fieldset is disabled or enabled.
    *
    * **The argument is the effective state, and taking it whole is what latched
@@ -48781,15 +48804,11 @@ export type CustomElements = {
    * the fieldset's hold is not recorded. There is no callback to learn it from
    * and reading `:disabled` here would answer about the attribute we are in the
    * middle of removing.
-   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
-   * not. The control shows no message for it: `reportValidity()` does that.
    * - `reportValidity() => boolean`: Returns whether the control is valid, and when it is not, fires `invalid`
    * and shows the browser's message at the control.
    * - `setCustomValidity(message: string) => void`: Marks the control invalid with `message`, or clears that with an empty
    * string, as on a native control. The form does not submit while it is set.
    * - `focus(options?: FocusOptions) => void`: Moves focus to the control, as focusing a native control does.
-   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
-   * form's `checkValidity()`, as connecting does for the form it starts in.
    *
    * ## CSS Custom Properties
    *
@@ -49220,8 +49239,9 @@ export type CustomElements = {
    * submitted nothing and sent no `helix-press`. The control's own click reaches
    * the host's listeners once, retargeted, as one from a native button does. A
    * disabled button does nothing, and a pending one refuses the press.
-   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
-   * form's `checkValidity()`, as connecting does for the form it starts in.
+   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the button's form changes. Its own rather than
+   * an override: the base a button extends watches no form's checks, because
+   * a button reports no verdict of its own.
    * - `formDisabledCallback(disabled: boolean) => void`: Called by the browser when an ancestor fieldset is disabled or enabled.
    *
    * **The argument is the effective state, and taking it whole is what latched
@@ -50104,6 +50124,10 @@ export type CustomElements = {
    * Falling back to what the markup declared rather than to empty, because
    * a restore with no state is a form the browser has nothing recorded for,
    * which is the same situation as a fresh one.
+   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
+   * not. The control shows no message for it: `reportValidity()` does that.
+   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
+   * form's `checkValidity()`, as connecting does for the form it starts in.
    * - `formDisabledCallback(disabled: boolean) => void`: Called by the browser when an ancestor fieldset is disabled or enabled.
    *
    * **The argument is the effective state, and taking it whole is what latched
@@ -50137,14 +50161,10 @@ export type CustomElements = {
    * the fieldset's hold is not recorded. There is no callback to learn it from
    * and reading `:disabled` here would answer about the attribute we are in the
    * middle of removing.
-   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
-   * not. The control shows no message for it: `reportValidity()` does that.
    * - `reportValidity() => boolean`: Returns whether the control is valid, and when it is not, fires `invalid`
    * and shows the browser's message at the control.
    * - `setCustomValidity(message: string) => void`: Marks the control invalid with `message`, or clears that with an empty
    * string, as on a native control. The form does not submit while it is set.
-   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
-   * form's `checkValidity()`, as connecting does for the form it starts in.
    *
    * ## CSS Custom Properties
    *
@@ -50521,6 +50541,10 @@ export type CustomElements = {
    * date picker dialog puts focus. Measured before this: from August 4, two
    * presses of Page Down, Escape, and Down again opened on October 4.
    * A `month` you set stays until the reader pages away from it.
+   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
+   * not. The control shows no message for it: `reportValidity()` does that.
+   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
+   * form's `checkValidity()`, as connecting does for the form it starts in.
    * - `formDisabledCallback(disabled: boolean) => void`: Called by the browser when an ancestor fieldset is disabled or enabled.
    *
    * **The argument is the effective state, and taking it whole is what latched
@@ -50554,14 +50578,10 @@ export type CustomElements = {
    * the fieldset's hold is not recorded. There is no callback to learn it from
    * and reading `:disabled` here would answer about the attribute we are in the
    * middle of removing.
-   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
-   * not. The control shows no message for it: `reportValidity()` does that.
    * - `reportValidity() => boolean`: Returns whether the control is valid, and when it is not, fires `invalid`
    * and shows the browser's message at the control.
    * - `setCustomValidity(message: string) => void`: Marks the control invalid with `message`, or clears that with an empty
    * string, as on a native control. The form does not submit while it is set.
-   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
-   * form's `checkValidity()`, as connecting does for the form it starts in.
    *
    * ## CSS Custom Properties
    *
@@ -52178,6 +52198,10 @@ export type CustomElements = {
    * mechanism a drop uses, so a file put in by dragging and one put in by the
    * picker come back out the same way.
    * - `focus(options?: FocusOptions) => void`: Moves focus to the control, as focusing a native control does.
+   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
+   * not. The control shows no message for it: `reportValidity()` does that.
+   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
+   * form's `checkValidity()`, as connecting does for the form it starts in.
    * - `formDisabledCallback(disabled: boolean) => void`: Called by the browser when an ancestor fieldset is disabled or enabled.
    *
    * **The argument is the effective state, and taking it whole is what latched
@@ -52211,14 +52235,10 @@ export type CustomElements = {
    * the fieldset's hold is not recorded. There is no callback to learn it from
    * and reading `:disabled` here would answer about the attribute we are in the
    * middle of removing.
-   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
-   * not. The control shows no message for it: `reportValidity()` does that.
    * - `reportValidity() => boolean`: Returns whether the control is valid, and when it is not, fires `invalid`
    * and shows the browser's message at the control.
    * - `setCustomValidity(message: string) => void`: Marks the control invalid with `message`, or clears that with an empty
    * string, as on a native control. The form does not submit while it is set.
-   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
-   * form's `checkValidity()`, as connecting does for the form it starts in.
    *
    * ## CSS Custom Properties
    *
@@ -53002,6 +53022,10 @@ export type CustomElements = {
    * which is the same situation as a fresh one.
    * - `setSelectionRange(start: number, end: number, direction?: 'backward' | 'forward' | 'none') => void`: Moves the caret, or selects a run of the text.
    * - `focus(options?: FocusOptions) => void`: Moves focus to the control, as focusing a native control does.
+   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
+   * not. The control shows no message for it: `reportValidity()` does that.
+   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
+   * form's `checkValidity()`, as connecting does for the form it starts in.
    * - `formDisabledCallback(disabled: boolean) => void`: Called by the browser when an ancestor fieldset is disabled or enabled.
    *
    * **The argument is the effective state, and taking it whole is what latched
@@ -53035,14 +53059,10 @@ export type CustomElements = {
    * the fieldset's hold is not recorded. There is no callback to learn it from
    * and reading `:disabled` here would answer about the attribute we are in the
    * middle of removing.
-   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
-   * not. The control shows no message for it: `reportValidity()` does that.
    * - `reportValidity() => boolean`: Returns whether the control is valid, and when it is not, fires `invalid`
    * and shows the browser's message at the control.
    * - `setCustomValidity(message: string) => void`: Marks the control invalid with `message`, or clears that with an empty
    * string, as on a native control. The form does not submit while it is set.
-   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
-   * form's `checkValidity()`, as connecting does for the form it starts in.
    *
    * ## CSS Custom Properties
    *
@@ -54397,8 +54417,9 @@ export type CustomElements = {
    * submitted nothing and sent no `helix-press`. The control's own click reaches
    * the host's listeners once, retargeted, as one from a native button does. A
    * disabled button does nothing, and a pending one refuses the press.
-   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
-   * form's `checkValidity()`, as connecting does for the form it starts in.
+   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the button's form changes. Its own rather than
+   * an override: the base a button extends watches no form's checks, because
+   * a button reports no verdict of its own.
    * - `formDisabledCallback(disabled: boolean) => void`: Called by the browser when an ancestor fieldset is disabled or enabled.
    *
    * **The argument is the effective state, and taking it whole is what latched
@@ -55008,6 +55029,10 @@ export type CustomElements = {
    * method does. It sends no event, as the native method sends none, and it
    * throws `InvalidStateError` on a type with no step, such as `text`.
    * - `stepDown(count = 1) => void`: Moves a number, a date or a time down by `step`, `count` times. See `stepUp`.
+   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
+   * not. The control shows no message for it: `reportValidity()` does that.
+   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
+   * form's `checkValidity()`, as connecting does for the form it starts in.
    * - `formDisabledCallback(disabled: boolean) => void`: Called by the browser when an ancestor fieldset is disabled or enabled.
    *
    * **The argument is the effective state, and taking it whole is what latched
@@ -55041,14 +55066,10 @@ export type CustomElements = {
    * the fieldset's hold is not recorded. There is no callback to learn it from
    * and reading `:disabled` here would answer about the attribute we are in the
    * middle of removing.
-   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
-   * not. The control shows no message for it: `reportValidity()` does that.
    * - `reportValidity() => boolean`: Returns whether the control is valid, and when it is not, fires `invalid`
    * and shows the browser's message at the control.
    * - `setCustomValidity(message: string) => void`: Marks the control invalid with `message`, or clears that with an empty
    * string, as on a native control. The form does not submit while it is set.
-   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
-   * form's `checkValidity()`, as connecting does for the form it starts in.
    *
    * ## CSS Custom Properties
    *
@@ -56682,6 +56703,10 @@ export type CustomElements = {
    * holds: without it the first arrow moved from the top of the list, so Down
    * from 14:07 went to midnight.
    * - `requestFilter(next: string) => boolean`: Requests a new filter, and returns whether the request went through.
+   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
+   * not. The control shows no message for it: `reportValidity()` does that.
+   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
+   * form's `checkValidity()`, as connecting does for the form it starts in.
    * - `formDisabledCallback(disabled: boolean) => void`: Called by the browser when an ancestor fieldset is disabled or enabled.
    *
    * **The argument is the effective state, and taking it whole is what latched
@@ -56715,15 +56740,11 @@ export type CustomElements = {
    * the fieldset's hold is not recorded. There is no callback to learn it from
    * and reading `:disabled` here would answer about the attribute we are in the
    * middle of removing.
-   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
-   * not. The control shows no message for it: `reportValidity()` does that.
    * - `reportValidity() => boolean`: Returns whether the control is valid, and when it is not, fires `invalid`
    * and shows the browser's message at the control.
    * - `setCustomValidity(message: string) => void`: Marks the control invalid with `message`, or clears that with an empty
    * string, as on a native control. The form does not submit while it is set.
    * - `focus(options?: FocusOptions) => void`: Moves focus to the control, as focusing a native control does.
-   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
-   * form's `checkValidity()`, as connecting does for the form it starts in.
    *
    * ## CSS Custom Properties
    *
@@ -59646,6 +59667,10 @@ export type CustomElements = {
    * having to repeat both.
    * - `focus(options?: FocusOptions) => void`: Moves focus to the control, as focusing a native control does.
    * - `select() => void`: Selects the number, so typing replaces it.
+   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
+   * not. The control shows no message for it: `reportValidity()` does that.
+   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
+   * form's `checkValidity()`, as connecting does for the form it starts in.
    * - `formDisabledCallback(disabled: boolean) => void`: Called by the browser when an ancestor fieldset is disabled or enabled.
    *
    * **The argument is the effective state, and taking it whole is what latched
@@ -59679,14 +59704,10 @@ export type CustomElements = {
    * the fieldset's hold is not recorded. There is no callback to learn it from
    * and reading `:disabled` here would answer about the attribute we are in the
    * middle of removing.
-   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
-   * not. The control shows no message for it: `reportValidity()` does that.
    * - `reportValidity() => boolean`: Returns whether the control is valid, and when it is not, fires `invalid`
    * and shows the browser's message at the control.
    * - `setCustomValidity(message: string) => void`: Marks the control invalid with `message`, or clears that with an empty
    * string, as on a native control. The form does not submit while it is set.
-   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
-   * form's `checkValidity()`, as connecting does for the form it starts in.
    *
    * ## CSS Custom Properties
    *
@@ -60896,6 +60917,10 @@ export type CustomElements = {
    * forgetting of a reader's past attempt, whose message otherwise showed over
    * the emptied control the moment the form was reset.
    * - `formStateRestoreCallback(state: string | File | FormData | null) => void`: Takes back the size a browser restores with the form, or the declared one.
+   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
+   * not. The control shows no message for it: `reportValidity()` does that.
+   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
+   * form's `checkValidity()`, as connecting does for the form it starts in.
    * - `formDisabledCallback(disabled: boolean) => void`: Called by the browser when an ancestor fieldset is disabled or enabled.
    *
    * **The argument is the effective state, and taking it whole is what latched
@@ -60929,15 +60954,11 @@ export type CustomElements = {
    * the fieldset's hold is not recorded. There is no callback to learn it from
    * and reading `:disabled` here would answer about the attribute we are in the
    * middle of removing.
-   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
-   * not. The control shows no message for it: `reportValidity()` does that.
    * - `reportValidity() => boolean`: Returns whether the control is valid, and when it is not, fires `invalid`
    * and shows the browser's message at the control.
    * - `setCustomValidity(message: string) => void`: Marks the control invalid with `message`, or clears that with an empty
    * string, as on a native control. The form does not submit while it is set.
    * - `focus(options?: FocusOptions) => void`: Moves focus to the control, as focusing a native control does.
-   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
-   * form's `checkValidity()`, as connecting does for the form it starts in.
    *
    * ## CSS Custom Properties
    *
@@ -61244,6 +61265,10 @@ export type CustomElements = {
    * which is the same situation as a fresh one.
    * - `focus(options?: FocusOptions) => void`: Moves focus to the control, as focusing a native control does.
    * - `clear() => void`: Empties every box and puts the caret in the first.
+   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
+   * not. The control shows no message for it: `reportValidity()` does that.
+   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
+   * form's `checkValidity()`, as connecting does for the form it starts in.
    * - `formDisabledCallback(disabled: boolean) => void`: Called by the browser when an ancestor fieldset is disabled or enabled.
    *
    * **The argument is the effective state, and taking it whole is what latched
@@ -61277,14 +61302,10 @@ export type CustomElements = {
    * the fieldset's hold is not recorded. There is no callback to learn it from
    * and reading `:disabled` here would answer about the attribute we are in the
    * middle of removing.
-   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
-   * not. The control shows no message for it: `reportValidity()` does that.
    * - `reportValidity() => boolean`: Returns whether the control is valid, and when it is not, fires `invalid`
    * and shows the browser's message at the control.
    * - `setCustomValidity(message: string) => void`: Marks the control invalid with `message`, or clears that with an empty
    * string, as on a native control. The form does not submit while it is set.
-   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
-   * form's `checkValidity()`, as connecting does for the form it starts in.
    *
    * ## CSS Custom Properties
    *
@@ -62042,6 +62063,10 @@ export type CustomElements = {
    * Falling back to what the markup declared rather than to empty, because
    * a restore with no state is a form the browser has nothing recorded for,
    * which is the same situation as a fresh one.
+   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
+   * not. The control shows no message for it: `reportValidity()` does that.
+   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
+   * form's `checkValidity()`, as connecting does for the form it starts in.
    * - `formDisabledCallback(disabled: boolean) => void`: Called by the browser when an ancestor fieldset is disabled or enabled.
    *
    * **The argument is the effective state, and taking it whole is what latched
@@ -62075,15 +62100,11 @@ export type CustomElements = {
    * the fieldset's hold is not recorded. There is no callback to learn it from
    * and reading `:disabled` here would answer about the attribute we are in the
    * middle of removing.
-   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
-   * not. The control shows no message for it: `reportValidity()` does that.
    * - `reportValidity() => boolean`: Returns whether the control is valid, and when it is not, fires `invalid`
    * and shows the browser's message at the control.
    * - `setCustomValidity(message: string) => void`: Marks the control invalid with `message`, or clears that with an empty
    * string, as on a native control. The form does not submit while it is set.
    * - `focus(options?: FocusOptions) => void`: Moves focus to the control, as focusing a native control does.
-   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
-   * form's `checkValidity()`, as connecting does for the form it starts in.
    *
    * ## CSS Custom Properties
    *
@@ -62543,6 +62564,10 @@ export type CustomElements = {
    * Falling back to what the markup declared rather than to empty, because
    * a restore with no state is a form the browser has nothing recorded for,
    * which is the same situation as a fresh one.
+   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
+   * not. The control shows no message for it: `reportValidity()` does that.
+   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
+   * form's `checkValidity()`, as connecting does for the form it starts in.
    * - `formDisabledCallback(disabled: boolean) => void`: Called by the browser when an ancestor fieldset is disabled or enabled.
    *
    * **The argument is the effective state, and taking it whole is what latched
@@ -62576,15 +62601,11 @@ export type CustomElements = {
    * the fieldset's hold is not recorded. There is no callback to learn it from
    * and reading `:disabled` here would answer about the attribute we are in the
    * middle of removing.
-   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
-   * not. The control shows no message for it: `reportValidity()` does that.
    * - `reportValidity() => boolean`: Returns whether the control is valid, and when it is not, fires `invalid`
    * and shows the browser's message at the control.
    * - `setCustomValidity(message: string) => void`: Marks the control invalid with `message`, or clears that with an empty
    * string, as on a native control. The form does not submit while it is set.
    * - `focus(options?: FocusOptions) => void`: Moves focus to the control, as focusing a native control does.
-   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
-   * form's `checkValidity()`, as connecting does for the form it starts in.
    *
    * ## CSS Custom Properties
    *
@@ -64154,6 +64175,10 @@ export type CustomElements = {
    * a restore with no state is a form the browser has nothing recorded for,
    * which is the same situation as a fresh one.
    * - `focus(options?: FocusOptions) => void`: Moves focus to the control, as focusing a native control does.
+   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
+   * not. The control shows no message for it: `reportValidity()` does that.
+   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
+   * form's `checkValidity()`, as connecting does for the form it starts in.
    * - `formDisabledCallback(disabled: boolean) => void`: Called by the browser when an ancestor fieldset is disabled or enabled.
    *
    * **The argument is the effective state, and taking it whole is what latched
@@ -64187,14 +64212,10 @@ export type CustomElements = {
    * the fieldset's hold is not recorded. There is no callback to learn it from
    * and reading `:disabled` here would answer about the attribute we are in the
    * middle of removing.
-   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
-   * not. The control shows no message for it: `reportValidity()` does that.
    * - `reportValidity() => boolean`: Returns whether the control is valid, and when it is not, fires `invalid`
    * and shows the browser's message at the control.
    * - `setCustomValidity(message: string) => void`: Marks the control invalid with `message`, or clears that with an empty
    * string, as on a native control. The form does not submit while it is set.
-   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
-   * form's `checkValidity()`, as connecting does for the form it starts in.
    *
    * ## CSS Custom Properties
    *
@@ -64655,6 +64676,10 @@ export type CustomElements = {
    * Falling back to what the markup declared rather than to empty, because
    * a restore with no state is a form the browser has nothing recorded for,
    * which is the same situation as a fresh one.
+   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
+   * not. The control shows no message for it: `reportValidity()` does that.
+   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
+   * form's `checkValidity()`, as connecting does for the form it starts in.
    * - `formDisabledCallback(disabled: boolean) => void`: Called by the browser when an ancestor fieldset is disabled or enabled.
    *
    * **The argument is the effective state, and taking it whole is what latched
@@ -64688,15 +64713,11 @@ export type CustomElements = {
    * the fieldset's hold is not recorded. There is no callback to learn it from
    * and reading `:disabled` here would answer about the attribute we are in the
    * middle of removing.
-   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
-   * not. The control shows no message for it: `reportValidity()` does that.
    * - `reportValidity() => boolean`: Returns whether the control is valid, and when it is not, fires `invalid`
    * and shows the browser's message at the control.
    * - `setCustomValidity(message: string) => void`: Marks the control invalid with `message`, or clears that with an empty
    * string, as on a native control. The form does not submit while it is set.
    * - `focus(options?: FocusOptions) => void`: Moves focus to the control, as focusing a native control does.
-   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
-   * form's `checkValidity()`, as connecting does for the form it starts in.
    *
    * ## CSS Custom Properties
    *
@@ -66383,6 +66404,10 @@ export type CustomElements = {
    * - `click() => void`: Turns the switch on or off, as `click()` does a native checkbox: passed to the control
    * inside, so the one click a listener hears is the control's, after it has
    * moved. See `HostClickController`.
+   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
+   * not. The control shows no message for it: `reportValidity()` does that.
+   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
+   * form's `checkValidity()`, as connecting does for the form it starts in.
    * - `formDisabledCallback(disabled: boolean) => void`: Called by the browser when an ancestor fieldset is disabled or enabled.
    *
    * **The argument is the effective state, and taking it whole is what latched
@@ -66416,15 +66441,11 @@ export type CustomElements = {
    * the fieldset's hold is not recorded. There is no callback to learn it from
    * and reading `:disabled` here would answer about the attribute we are in the
    * middle of removing.
-   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
-   * not. The control shows no message for it: `reportValidity()` does that.
    * - `reportValidity() => boolean`: Returns whether the control is valid, and when it is not, fires `invalid`
    * and shows the browser's message at the control.
    * - `setCustomValidity(message: string) => void`: Marks the control invalid with `message`, or clears that with an empty
    * string, as on a native control. The form does not submit while it is set.
    * - `focus(options?: FocusOptions) => void`: Moves focus to the control, as focusing a native control does.
-   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
-   * form's `checkValidity()`, as connecting does for the form it starts in.
    *
    * ## CSS Custom Properties
    *
@@ -68008,6 +68029,10 @@ export type CustomElements = {
    * selected after. It sends no event, as the native method sends none.
    * - `select() => void`: Selects everything in the field.
    * - `focus(options?: FocusOptions) => void`: Moves focus to the control, as focusing a native control does.
+   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
+   * not. The control shows no message for it: `reportValidity()` does that.
+   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
+   * form's `checkValidity()`, as connecting does for the form it starts in.
    * - `formDisabledCallback(disabled: boolean) => void`: Called by the browser when an ancestor fieldset is disabled or enabled.
    *
    * **The argument is the effective state, and taking it whole is what latched
@@ -68041,14 +68066,10 @@ export type CustomElements = {
    * the fieldset's hold is not recorded. There is no callback to learn it from
    * and reading `:disabled` here would answer about the attribute we are in the
    * middle of removing.
-   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
-   * not. The control shows no message for it: `reportValidity()` does that.
    * - `reportValidity() => boolean`: Returns whether the control is valid, and when it is not, fires `invalid`
    * and shows the browser's message at the control.
    * - `setCustomValidity(message: string) => void`: Marks the control invalid with `message`, or clears that with an empty
    * string, as on a native control. The form does not submit while it is set.
-   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
-   * form's `checkValidity()`, as connecting does for the form it starts in.
    *
    * ## CSS Custom Properties
    *
@@ -68375,6 +68396,10 @@ export type CustomElements = {
    * Falling back to what the markup declared rather than to empty, because
    * a restore with no state is a form the browser has nothing recorded for,
    * which is the same situation as a fresh one.
+   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
+   * not. The control shows no message for it: `reportValidity()` does that.
+   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
+   * form's `checkValidity()`, as connecting does for the form it starts in.
    * - `formDisabledCallback(disabled: boolean) => void`: Called by the browser when an ancestor fieldset is disabled or enabled.
    *
    * **The argument is the effective state, and taking it whole is what latched
@@ -68408,14 +68433,10 @@ export type CustomElements = {
    * the fieldset's hold is not recorded. There is no callback to learn it from
    * and reading `:disabled` here would answer about the attribute we are in the
    * middle of removing.
-   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
-   * not. The control shows no message for it: `reportValidity()` does that.
    * - `reportValidity() => boolean`: Returns whether the control is valid, and when it is not, fires `invalid`
    * and shows the browser's message at the control.
    * - `setCustomValidity(message: string) => void`: Marks the control invalid with `message`, or clears that with an empty
    * string, as on a native control. The form does not submit while it is set.
-   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
-   * form's `checkValidity()`, as connecting does for the form it starts in.
    *
    * ## CSS Custom Properties
    *
@@ -68834,6 +68855,10 @@ export type CustomElements = {
    * calls this again afterwards. The guard below makes the early call harmless
    * rather than wrong, which is why it can be left in.
    * - `focus(options?: FocusOptions) => void`: Moves focus to the control, as focusing a native control does.
+   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
+   * not. The control shows no message for it: `reportValidity()` does that.
+   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
+   * form's `checkValidity()`, as connecting does for the form it starts in.
    * - `formDisabledCallback(disabled: boolean) => void`: Called by the browser when an ancestor fieldset is disabled or enabled.
    *
    * **The argument is the effective state, and taking it whole is what latched
@@ -68867,14 +68892,10 @@ export type CustomElements = {
    * the fieldset's hold is not recorded. There is no callback to learn it from
    * and reading `:disabled` here would answer about the attribute we are in the
    * middle of removing.
-   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
-   * not. The control shows no message for it: `reportValidity()` does that.
    * - `reportValidity() => boolean`: Returns whether the control is valid, and when it is not, fires `invalid`
    * and shows the browser's message at the control.
    * - `setCustomValidity(message: string) => void`: Marks the control invalid with `message`, or clears that with an empty
    * string, as on a native control. The form does not submit while it is set.
-   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
-   * form's `checkValidity()`, as connecting does for the form it starts in.
    *
    * ## CSS Custom Properties
    *
@@ -69650,6 +69671,10 @@ export type CustomElements = {
    * Falling back to what the markup declared rather than to empty, because
    * a restore with no state is a form the browser has nothing recorded for,
    * which is the same situation as a fresh one.
+   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
+   * not. The control shows no message for it: `reportValidity()` does that.
+   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
+   * form's `checkValidity()`, as connecting does for the form it starts in.
    * - `formDisabledCallback(disabled: boolean) => void`: Called by the browser when an ancestor fieldset is disabled or enabled.
    *
    * **The argument is the effective state, and taking it whole is what latched
@@ -69683,15 +69708,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
    *
@@ -71851,6 +71872,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.
    *
@@ -71873,13 +71900,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
@@ -73884,6 +73912,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.
@@ -74629,7 +74658,9 @@ export type CustomElementsSolidJs = {
    * submitted nothing and sent no `helix-press`. The control's own click reaches
    * the host's listeners once, retargeted, as one from a native button does. A
    * disabled button does nothing, and a pending one refuses the press.
-   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the button's form changes.
+   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the button's form changes. Its own rather than
+   * an override: the base a button extends watches no form's checks, because
+   * a button reports no verdict of its own.
    * - `formDisabledCallback(disabled: boolean) => void`: Called by the browser when an ancestor fieldset is disabled or enabled.
    *
    * **The argument is the effective state, and taking it whole is what latched
@@ -76184,6 +76215,10 @@ export type CustomElementsSolidJs = {
    * forgetting of a reader's past attempt, whose message otherwise showed over
    * the emptied control the moment the form was reset.
    * - `formStateRestoreCallback(state: string | File | FormData | null) => void`: Brings back the draft when the browser restores the form.
+   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
+   * not. The control shows no message for it: `reportValidity()` does that.
+   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
+   * form's `checkValidity()`, as connecting does for the form it starts in.
    * - `formDisabledCallback(disabled: boolean) => void`: Called by the browser when an ancestor fieldset is disabled or enabled.
    *
    * **The argument is the effective state, and taking it whole is what latched
@@ -76217,15 +76252,11 @@ export type CustomElementsSolidJs = {
    * the fieldset's hold is not recorded. There is no callback to learn it from
    * and reading `:disabled` here would answer about the attribute we are in the
    * middle of removing.
-   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
-   * not. The control shows no message for it: `reportValidity()` does that.
    * - `reportValidity() => boolean`: Returns whether the control is valid, and when it is not, fires `invalid`
    * and shows the browser's message at the control.
    * - `setCustomValidity(message: string) => void`: Marks the control invalid with `message`, or clears that with an empty
    * string, as on a native control. The form does not submit while it is set.
    * - `focus(options?: FocusOptions) => void`: Moves focus to the control, as focusing a native control does.
-   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
-   * form's `checkValidity()`, as connecting does for the form it starts in.
    *
    * ## CSS Custom Properties
    *
@@ -76757,6 +76788,10 @@ export type CustomElementsSolidJs = {
    *
    * Through the base's prototype rather than `super`, because the base this
    * grafts onto is any element and only a form element has the hook.
+   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
+   * not. The control shows no message for it: `reportValidity()` does that.
+   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
+   * form's `checkValidity()`, as connecting does for the form it starts in.
    * - `formDisabledCallback(disabled: boolean) => void`: Called by the browser when an ancestor fieldset is disabled or enabled.
    *
    * **The argument is the effective state, and taking it whole is what latched
@@ -76790,15 +76825,11 @@ export type CustomElementsSolidJs = {
    * the fieldset's hold is not recorded. There is no callback to learn it from
    * and reading `:disabled` here would answer about the attribute we are in the
    * middle of removing.
-   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
-   * not. The control shows no message for it: `reportValidity()` does that.
    * - `reportValidity() => boolean`: Returns whether the control is valid, and when it is not, fires `invalid`
    * and shows the browser's message at the control.
    * - `setCustomValidity(message: string) => void`: Marks the control invalid with `message`, or clears that with an empty
    * string, as on a native control. The form does not submit while it is set.
    * - `focus(options?: FocusOptions) => void`: Moves focus to the control, as focusing a native control does.
-   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
-   * form's `checkValidity()`, as connecting does for the form it starts in.
    *
    * ## CSS Custom Properties
    *
@@ -77046,6 +77077,10 @@ export type CustomElementsSolidJs = {
    * - `click() => void`: Ticks or clears the box, as `click()` does a native checkbox: passed to the control
    * inside, so the one click a listener hears is the control's, after it has
    * moved. See `HostClickController`.
+   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
+   * not. The control shows no message for it: `reportValidity()` does that.
+   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
+   * form's `checkValidity()`, as connecting does for the form it starts in.
    * - `formDisabledCallback(disabled: boolean) => void`: Called by the browser when an ancestor fieldset is disabled or enabled.
    *
    * **The argument is the effective state, and taking it whole is what latched
@@ -77079,15 +77114,11 @@ export type CustomElementsSolidJs = {
    * the fieldset's hold is not recorded. There is no callback to learn it from
    * and reading `:disabled` here would answer about the attribute we are in the
    * middle of removing.
-   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
-   * not. The control shows no message for it: `reportValidity()` does that.
    * - `reportValidity() => boolean`: Returns whether the control is valid, and when it is not, fires `invalid`
    * and shows the browser's message at the control.
    * - `setCustomValidity(message: string) => void`: Marks the control invalid with `message`, or clears that with an empty
    * string, as on a native control. The form does not submit while it is set.
    * - `focus(options?: FocusOptions) => void`: Moves focus to the control, as focusing a native control does.
-   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
-   * form's `checkValidity()`, as connecting does for the form it starts in.
    *
    * ## CSS Custom Properties
    *
@@ -77707,6 +77738,10 @@ export type CustomElementsSolidJs = {
    * Falling back to what the markup declared rather than to empty, because
    * a restore with no state is a form the browser has nothing recorded for,
    * which is the same situation as a fresh one.
+   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
+   * not. The control shows no message for it: `reportValidity()` does that.
+   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
+   * form's `checkValidity()`, as connecting does for the form it starts in.
    * - `formDisabledCallback(disabled: boolean) => void`: Called by the browser when an ancestor fieldset is disabled or enabled.
    *
    * **The argument is the effective state, and taking it whole is what latched
@@ -77740,14 +77775,10 @@ export type CustomElementsSolidJs = {
    * the fieldset's hold is not recorded. There is no callback to learn it from
    * and reading `:disabled` here would answer about the attribute we are in the
    * middle of removing.
-   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
-   * not. The control shows no message for it: `reportValidity()` does that.
    * - `reportValidity() => boolean`: Returns whether the control is valid, and when it is not, fires `invalid`
    * and shows the browser's message at the control.
    * - `setCustomValidity(message: string) => void`: Marks the control invalid with `message`, or clears that with an empty
    * string, as on a native control. The form does not submit while it is set.
-   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
-   * form's `checkValidity()`, as connecting does for the form it starts in.
    *
    * ## CSS Custom Properties
    *
@@ -78122,6 +78153,10 @@ export type CustomElementsSolidJs = {
    * a restore with no state is a form the browser has nothing recorded for,
    * which is the same situation as a fresh one.
    * - `focus(options?: FocusOptions) => void`: Moves focus to the control, as focusing a native control does.
+   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
+   * not. The control shows no message for it: `reportValidity()` does that.
+   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
+   * form's `checkValidity()`, as connecting does for the form it starts in.
    * - `formDisabledCallback(disabled: boolean) => void`: Called by the browser when an ancestor fieldset is disabled or enabled.
    *
    * **The argument is the effective state, and taking it whole is what latched
@@ -78155,14 +78190,10 @@ export type CustomElementsSolidJs = {
    * the fieldset's hold is not recorded. There is no callback to learn it from
    * and reading `:disabled` here would answer about the attribute we are in the
    * middle of removing.
-   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
-   * not. The control shows no message for it: `reportValidity()` does that.
    * - `reportValidity() => boolean`: Returns whether the control is valid, and when it is not, fires `invalid`
    * and shows the browser's message at the control.
    * - `setCustomValidity(message: string) => void`: Marks the control invalid with `message`, or clears that with an empty
    * string, as on a native control. The form does not submit while it is set.
-   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
-   * form's `checkValidity()`, as connecting does for the form it starts in.
    *
    * ## CSS Custom Properties
    *
@@ -78544,6 +78575,10 @@ export type CustomElementsSolidJs = {
    * Falling back to what the markup declared rather than to empty, because
    * a restore with no state is a form the browser has nothing recorded for,
    * which is the same situation as a fresh one.
+   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
+   * not. The control shows no message for it: `reportValidity()` does that.
+   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
+   * form's `checkValidity()`, as connecting does for the form it starts in.
    * - `formDisabledCallback(disabled: boolean) => void`: Called by the browser when an ancestor fieldset is disabled or enabled.
    *
    * **The argument is the effective state, and taking it whole is what latched
@@ -78577,15 +78612,11 @@ export type CustomElementsSolidJs = {
    * the fieldset's hold is not recorded. There is no callback to learn it from
    * and reading `:disabled` here would answer about the attribute we are in the
    * middle of removing.
-   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
-   * not. The control shows no message for it: `reportValidity()` does that.
    * - `reportValidity() => boolean`: Returns whether the control is valid, and when it is not, fires `invalid`
    * and shows the browser's message at the control.
    * - `setCustomValidity(message: string) => void`: Marks the control invalid with `message`, or clears that with an empty
    * string, as on a native control. The form does not submit while it is set.
    * - `focus(options?: FocusOptions) => void`: Moves focus to the control, as focusing a native control does.
-   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
-   * form's `checkValidity()`, as connecting does for the form it starts in.
    *
    * ## CSS Custom Properties
    *
@@ -79022,8 +79053,9 @@ export type CustomElementsSolidJs = {
    * submitted nothing and sent no `helix-press`. The control's own click reaches
    * the host's listeners once, retargeted, as one from a native button does. A
    * disabled button does nothing, and a pending one refuses the press.
-   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
-   * form's `checkValidity()`, as connecting does for the form it starts in.
+   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the button's form changes. Its own rather than
+   * an override: the base a button extends watches no form's checks, because
+   * a button reports no verdict of its own.
    * - `formDisabledCallback(disabled: boolean) => void`: Called by the browser when an ancestor fieldset is disabled or enabled.
    *
    * **The argument is the effective state, and taking it whole is what latched
@@ -79912,6 +79944,10 @@ export type CustomElementsSolidJs = {
    * Falling back to what the markup declared rather than to empty, because
    * a restore with no state is a form the browser has nothing recorded for,
    * which is the same situation as a fresh one.
+   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
+   * not. The control shows no message for it: `reportValidity()` does that.
+   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
+   * form's `checkValidity()`, as connecting does for the form it starts in.
    * - `formDisabledCallback(disabled: boolean) => void`: Called by the browser when an ancestor fieldset is disabled or enabled.
    *
    * **The argument is the effective state, and taking it whole is what latched
@@ -79945,14 +79981,10 @@ export type CustomElementsSolidJs = {
    * the fieldset's hold is not recorded. There is no callback to learn it from
    * and reading `:disabled` here would answer about the attribute we are in the
    * middle of removing.
-   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
-   * not. The control shows no message for it: `reportValidity()` does that.
    * - `reportValidity() => boolean`: Returns whether the control is valid, and when it is not, fires `invalid`
    * and shows the browser's message at the control.
    * - `setCustomValidity(message: string) => void`: Marks the control invalid with `message`, or clears that with an empty
    * string, as on a native control. The form does not submit while it is set.
-   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
-   * form's `checkValidity()`, as connecting does for the form it starts in.
    *
    * ## CSS Custom Properties
    *
@@ -80332,6 +80364,10 @@ export type CustomElementsSolidJs = {
    * date picker dialog puts focus. Measured before this: from August 4, two
    * presses of Page Down, Escape, and Down again opened on October 4.
    * A `month` you set stays until the reader pages away from it.
+   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
+   * not. The control shows no message for it: `reportValidity()` does that.
+   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
+   * form's `checkValidity()`, as connecting does for the form it starts in.
    * - `formDisabledCallback(disabled: boolean) => void`: Called by the browser when an ancestor fieldset is disabled or enabled.
    *
    * **The argument is the effective state, and taking it whole is what latched
@@ -80365,14 +80401,10 @@ export type CustomElementsSolidJs = {
    * the fieldset's hold is not recorded. There is no callback to learn it from
    * and reading `:disabled` here would answer about the attribute we are in the
    * middle of removing.
-   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
-   * not. The control shows no message for it: `reportValidity()` does that.
    * - `reportValidity() => boolean`: Returns whether the control is valid, and when it is not, fires `invalid`
    * and shows the browser's message at the control.
    * - `setCustomValidity(message: string) => void`: Marks the control invalid with `message`, or clears that with an empty
    * string, as on a native control. The form does not submit while it is set.
-   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
-   * form's `checkValidity()`, as connecting does for the form it starts in.
    *
    * ## CSS Custom Properties
    *
@@ -82019,6 +82051,10 @@ export type CustomElementsSolidJs = {
    * mechanism a drop uses, so a file put in by dragging and one put in by the
    * picker come back out the same way.
    * - `focus(options?: FocusOptions) => void`: Moves focus to the control, as focusing a native control does.
+   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
+   * not. The control shows no message for it: `reportValidity()` does that.
+   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
+   * form's `checkValidity()`, as connecting does for the form it starts in.
    * - `formDisabledCallback(disabled: boolean) => void`: Called by the browser when an ancestor fieldset is disabled or enabled.
    *
    * **The argument is the effective state, and taking it whole is what latched
@@ -82052,14 +82088,10 @@ export type CustomElementsSolidJs = {
    * the fieldset's hold is not recorded. There is no callback to learn it from
    * and reading `:disabled` here would answer about the attribute we are in the
    * middle of removing.
-   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
-   * not. The control shows no message for it: `reportValidity()` does that.
    * - `reportValidity() => boolean`: Returns whether the control is valid, and when it is not, fires `invalid`
    * and shows the browser's message at the control.
    * - `setCustomValidity(message: string) => void`: Marks the control invalid with `message`, or clears that with an empty
    * string, as on a native control. The form does not submit while it is set.
-   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
-   * form's `checkValidity()`, as connecting does for the form it starts in.
    *
    * ## CSS Custom Properties
    *
@@ -82858,6 +82890,10 @@ export type CustomElementsSolidJs = {
    * which is the same situation as a fresh one.
    * - `setSelectionRange(start: number, end: number, direction?: 'backward' | 'forward' | 'none') => void`: Moves the caret, or selects a run of the text.
    * - `focus(options?: FocusOptions) => void`: Moves focus to the control, as focusing a native control does.
+   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
+   * not. The control shows no message for it: `reportValidity()` does that.
+   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
+   * form's `checkValidity()`, as connecting does for the form it starts in.
    * - `formDisabledCallback(disabled: boolean) => void`: Called by the browser when an ancestor fieldset is disabled or enabled.
    *
    * **The argument is the effective state, and taking it whole is what latched
@@ -82891,14 +82927,10 @@ export type CustomElementsSolidJs = {
    * the fieldset's hold is not recorded. There is no callback to learn it from
    * and reading `:disabled` here would answer about the attribute we are in the
    * middle of removing.
-   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
-   * not. The control shows no message for it: `reportValidity()` does that.
    * - `reportValidity() => boolean`: Returns whether the control is valid, and when it is not, fires `invalid`
    * and shows the browser's message at the control.
    * - `setCustomValidity(message: string) => void`: Marks the control invalid with `message`, or clears that with an empty
    * string, as on a native control. The form does not submit while it is set.
-   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
-   * form's `checkValidity()`, as connecting does for the form it starts in.
    *
    * ## CSS Custom Properties
    *
@@ -84271,8 +84303,9 @@ export type CustomElementsSolidJs = {
    * submitted nothing and sent no `helix-press`. The control's own click reaches
    * the host's listeners once, retargeted, as one from a native button does. A
    * disabled button does nothing, and a pending one refuses the press.
-   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
-   * form's `checkValidity()`, as connecting does for the form it starts in.
+   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the button's form changes. Its own rather than
+   * an override: the base a button extends watches no form's checks, because
+   * a button reports no verdict of its own.
    * - `formDisabledCallback(disabled: boolean) => void`: Called by the browser when an ancestor fieldset is disabled or enabled.
    *
    * **The argument is the effective state, and taking it whole is what latched
@@ -84892,6 +84925,10 @@ export type CustomElementsSolidJs = {
    * method does. It sends no event, as the native method sends none, and it
    * throws `InvalidStateError` on a type with no step, such as `text`.
    * - `stepDown(count = 1) => void`: Moves a number, a date or a time down by `step`, `count` times. See `stepUp`.
+   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
+   * not. The control shows no message for it: `reportValidity()` does that.
+   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
+   * form's `checkValidity()`, as connecting does for the form it starts in.
    * - `formDisabledCallback(disabled: boolean) => void`: Called by the browser when an ancestor fieldset is disabled or enabled.
    *
    * **The argument is the effective state, and taking it whole is what latched
@@ -84925,14 +84962,10 @@ export type CustomElementsSolidJs = {
    * the fieldset's hold is not recorded. There is no callback to learn it from
    * and reading `:disabled` here would answer about the attribute we are in the
    * middle of removing.
-   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
-   * not. The control shows no message for it: `reportValidity()` does that.
    * - `reportValidity() => boolean`: Returns whether the control is valid, and when it is not, fires `invalid`
    * and shows the browser's message at the control.
    * - `setCustomValidity(message: string) => void`: Marks the control invalid with `message`, or clears that with an empty
    * string, as on a native control. The form does not submit while it is set.
-   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
-   * form's `checkValidity()`, as connecting does for the form it starts in.
    *
    * ## CSS Custom Properties
    *
@@ -86590,6 +86623,10 @@ export type CustomElementsSolidJs = {
    * holds: without it the first arrow moved from the top of the list, so Down
    * from 14:07 went to midnight.
    * - `requestFilter(next: string) => boolean`: Requests a new filter, and returns whether the request went through.
+   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
+   * not. The control shows no message for it: `reportValidity()` does that.
+   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
+   * form's `checkValidity()`, as connecting does for the form it starts in.
    * - `formDisabledCallback(disabled: boolean) => void`: Called by the browser when an ancestor fieldset is disabled or enabled.
    *
    * **The argument is the effective state, and taking it whole is what latched
@@ -86623,15 +86660,11 @@ export type CustomElementsSolidJs = {
    * the fieldset's hold is not recorded. There is no callback to learn it from
    * and reading `:disabled` here would answer about the attribute we are in the
    * middle of removing.
-   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
-   * not. The control shows no message for it: `reportValidity()` does that.
    * - `reportValidity() => boolean`: Returns whether the control is valid, and when it is not, fires `invalid`
    * and shows the browser's message at the control.
    * - `setCustomValidity(message: string) => void`: Marks the control invalid with `message`, or clears that with an empty
    * string, as on a native control. The form does not submit while it is set.
    * - `focus(options?: FocusOptions) => void`: Moves focus to the control, as focusing a native control does.
-   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
-   * form's `checkValidity()`, as connecting does for the form it starts in.
    *
    * ## CSS Custom Properties
    *
@@ -89620,6 +89653,10 @@ export type CustomElementsSolidJs = {
    * having to repeat both.
    * - `focus(options?: FocusOptions) => void`: Moves focus to the control, as focusing a native control does.
    * - `select() => void`: Selects the number, so typing replaces it.
+   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
+   * not. The control shows no message for it: `reportValidity()` does that.
+   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
+   * form's `checkValidity()`, as connecting does for the form it starts in.
    * - `formDisabledCallback(disabled: boolean) => void`: Called by the browser when an ancestor fieldset is disabled or enabled.
    *
    * **The argument is the effective state, and taking it whole is what latched
@@ -89653,14 +89690,10 @@ export type CustomElementsSolidJs = {
    * the fieldset's hold is not recorded. There is no callback to learn it from
    * and reading `:disabled` here would answer about the attribute we are in the
    * middle of removing.
-   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
-   * not. The control shows no message for it: `reportValidity()` does that.
    * - `reportValidity() => boolean`: Returns whether the control is valid, and when it is not, fires `invalid`
    * and shows the browser's message at the control.
    * - `setCustomValidity(message: string) => void`: Marks the control invalid with `message`, or clears that with an empty
    * string, as on a native control. The form does not submit while it is set.
-   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
-   * form's `checkValidity()`, as connecting does for the form it starts in.
    *
    * ## CSS Custom Properties
    *
@@ -90893,6 +90926,10 @@ export type CustomElementsSolidJs = {
    * forgetting of a reader's past attempt, whose message otherwise showed over
    * the emptied control the moment the form was reset.
    * - `formStateRestoreCallback(state: string | File | FormData | null) => void`: Takes back the size a browser restores with the form, or the declared one.
+   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
+   * not. The control shows no message for it: `reportValidity()` does that.
+   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
+   * form's `checkValidity()`, as connecting does for the form it starts in.
    * - `formDisabledCallback(disabled: boolean) => void`: Called by the browser when an ancestor fieldset is disabled or enabled.
    *
    * **The argument is the effective state, and taking it whole is what latched
@@ -90926,15 +90963,11 @@ export type CustomElementsSolidJs = {
    * the fieldset's hold is not recorded. There is no callback to learn it from
    * and reading `:disabled` here would answer about the attribute we are in the
    * middle of removing.
-   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
-   * not. The control shows no message for it: `reportValidity()` does that.
    * - `reportValidity() => boolean`: Returns whether the control is valid, and when it is not, fires `invalid`
    * and shows the browser's message at the control.
    * - `setCustomValidity(message: string) => void`: Marks the control invalid with `message`, or clears that with an empty
    * string, as on a native control. The form does not submit while it is set.
    * - `focus(options?: FocusOptions) => void`: Moves focus to the control, as focusing a native control does.
-   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
-   * form's `checkValidity()`, as connecting does for the form it starts in.
    *
    * ## CSS Custom Properties
    *
@@ -91247,6 +91280,10 @@ export type CustomElementsSolidJs = {
    * which is the same situation as a fresh one.
    * - `focus(options?: FocusOptions) => void`: Moves focus to the control, as focusing a native control does.
    * - `clear() => void`: Empties every box and puts the caret in the first.
+   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
+   * not. The control shows no message for it: `reportValidity()` does that.
+   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
+   * form's `checkValidity()`, as connecting does for the form it starts in.
    * - `formDisabledCallback(disabled: boolean) => void`: Called by the browser when an ancestor fieldset is disabled or enabled.
    *
    * **The argument is the effective state, and taking it whole is what latched
@@ -91280,14 +91317,10 @@ export type CustomElementsSolidJs = {
    * the fieldset's hold is not recorded. There is no callback to learn it from
    * and reading `:disabled` here would answer about the attribute we are in the
    * middle of removing.
-   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
-   * not. The control shows no message for it: `reportValidity()` does that.
    * - `reportValidity() => boolean`: Returns whether the control is valid, and when it is not, fires `invalid`
    * and shows the browser's message at the control.
    * - `setCustomValidity(message: string) => void`: Marks the control invalid with `message`, or clears that with an empty
    * string, as on a native control. The form does not submit while it is set.
-   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
-   * form's `checkValidity()`, as connecting does for the form it starts in.
    *
    * ## CSS Custom Properties
    *
@@ -92062,6 +92095,10 @@ export type CustomElementsSolidJs = {
    * Falling back to what the markup declared rather than to empty, because
    * a restore with no state is a form the browser has nothing recorded for,
    * which is the same situation as a fresh one.
+   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
+   * not. The control shows no message for it: `reportValidity()` does that.
+   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
+   * form's `checkValidity()`, as connecting does for the form it starts in.
    * - `formDisabledCallback(disabled: boolean) => void`: Called by the browser when an ancestor fieldset is disabled or enabled.
    *
    * **The argument is the effective state, and taking it whole is what latched
@@ -92095,15 +92132,11 @@ export type CustomElementsSolidJs = {
    * the fieldset's hold is not recorded. There is no callback to learn it from
    * and reading `:disabled` here would answer about the attribute we are in the
    * middle of removing.
-   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
-   * not. The control shows no message for it: `reportValidity()` does that.
    * - `reportValidity() => boolean`: Returns whether the control is valid, and when it is not, fires `invalid`
    * and shows the browser's message at the control.
    * - `setCustomValidity(message: string) => void`: Marks the control invalid with `message`, or clears that with an empty
    * string, as on a native control. The form does not submit while it is set.
    * - `focus(options?: FocusOptions) => void`: Moves focus to the control, as focusing a native control does.
-   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
-   * form's `checkValidity()`, as connecting does for the form it starts in.
    *
    * ## CSS Custom Properties
    *
@@ -92571,6 +92604,10 @@ export type CustomElementsSolidJs = {
    * Falling back to what the markup declared rather than to empty, because
    * a restore with no state is a form the browser has nothing recorded for,
    * which is the same situation as a fresh one.
+   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
+   * not. The control shows no message for it: `reportValidity()` does that.
+   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
+   * form's `checkValidity()`, as connecting does for the form it starts in.
    * - `formDisabledCallback(disabled: boolean) => void`: Called by the browser when an ancestor fieldset is disabled or enabled.
    *
    * **The argument is the effective state, and taking it whole is what latched
@@ -92604,15 +92641,11 @@ export type CustomElementsSolidJs = {
    * the fieldset's hold is not recorded. There is no callback to learn it from
    * and reading `:disabled` here would answer about the attribute we are in the
    * middle of removing.
-   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
-   * not. The control shows no message for it: `reportValidity()` does that.
    * - `reportValidity() => boolean`: Returns whether the control is valid, and when it is not, fires `invalid`
    * and shows the browser's message at the control.
    * - `setCustomValidity(message: string) => void`: Marks the control invalid with `message`, or clears that with an empty
    * string, as on a native control. The form does not submit while it is set.
    * - `focus(options?: FocusOptions) => void`: Moves focus to the control, as focusing a native control does.
-   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
-   * form's `checkValidity()`, as connecting does for the form it starts in.
    *
    * ## CSS Custom Properties
    *
@@ -94209,6 +94242,10 @@ export type CustomElementsSolidJs = {
    * a restore with no state is a form the browser has nothing recorded for,
    * which is the same situation as a fresh one.
    * - `focus(options?: FocusOptions) => void`: Moves focus to the control, as focusing a native control does.
+   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
+   * not. The control shows no message for it: `reportValidity()` does that.
+   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
+   * form's `checkValidity()`, as connecting does for the form it starts in.
    * - `formDisabledCallback(disabled: boolean) => void`: Called by the browser when an ancestor fieldset is disabled or enabled.
    *
    * **The argument is the effective state, and taking it whole is what latched
@@ -94242,14 +94279,10 @@ export type CustomElementsSolidJs = {
    * the fieldset's hold is not recorded. There is no callback to learn it from
    * and reading `:disabled` here would answer about the attribute we are in the
    * middle of removing.
-   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
-   * not. The control shows no message for it: `reportValidity()` does that.
    * - `reportValidity() => boolean`: Returns whether the control is valid, and when it is not, fires `invalid`
    * and shows the browser's message at the control.
    * - `setCustomValidity(message: string) => void`: Marks the control invalid with `message`, or clears that with an empty
    * string, as on a native control. The form does not submit while it is set.
-   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
-   * form's `checkValidity()`, as connecting does for the form it starts in.
    *
    * ## CSS Custom Properties
    *
@@ -94719,6 +94752,10 @@ export type CustomElementsSolidJs = {
    * Falling back to what the markup declared rather than to empty, because
    * a restore with no state is a form the browser has nothing recorded for,
    * which is the same situation as a fresh one.
+   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
+   * not. The control shows no message for it: `reportValidity()` does that.
+   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
+   * form's `checkValidity()`, as connecting does for the form it starts in.
    * - `formDisabledCallback(disabled: boolean) => void`: Called by the browser when an ancestor fieldset is disabled or enabled.
    *
    * **The argument is the effective state, and taking it whole is what latched
@@ -94752,15 +94789,11 @@ export type CustomElementsSolidJs = {
    * the fieldset's hold is not recorded. There is no callback to learn it from
    * and reading `:disabled` here would answer about the attribute we are in the
    * middle of removing.
-   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
-   * not. The control shows no message for it: `reportValidity()` does that.
    * - `reportValidity() => boolean`: Returns whether the control is valid, and when it is not, fires `invalid`
    * and shows the browser's message at the control.
    * - `setCustomValidity(message: string) => void`: Marks the control invalid with `message`, or clears that with an empty
    * string, as on a native control. The form does not submit while it is set.
    * - `focus(options?: FocusOptions) => void`: Moves focus to the control, as focusing a native control does.
-   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
-   * form's `checkValidity()`, as connecting does for the form it starts in.
    *
    * ## CSS Custom Properties
    *
@@ -96483,6 +96516,10 @@ export type CustomElementsSolidJs = {
    * - `click() => void`: Turns the switch on or off, as `click()` does a native checkbox: passed to the control
    * inside, so the one click a listener hears is the control's, after it has
    * moved. See `HostClickController`.
+   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
+   * not. The control shows no message for it: `reportValidity()` does that.
+   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
+   * form's `checkValidity()`, as connecting does for the form it starts in.
    * - `formDisabledCallback(disabled: boolean) => void`: Called by the browser when an ancestor fieldset is disabled or enabled.
    *
    * **The argument is the effective state, and taking it whole is what latched
@@ -96516,15 +96553,11 @@ export type CustomElementsSolidJs = {
    * the fieldset's hold is not recorded. There is no callback to learn it from
    * and reading `:disabled` here would answer about the attribute we are in the
    * middle of removing.
-   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
-   * not. The control shows no message for it: `reportValidity()` does that.
    * - `reportValidity() => boolean`: Returns whether the control is valid, and when it is not, fires `invalid`
    * and shows the browser's message at the control.
    * - `setCustomValidity(message: string) => void`: Marks the control invalid with `message`, or clears that with an empty
    * string, as on a native control. The form does not submit while it is set.
    * - `focus(options?: FocusOptions) => void`: Moves focus to the control, as focusing a native control does.
-   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
-   * form's `checkValidity()`, as connecting does for the form it starts in.
    *
    * ## CSS Custom Properties
    *
@@ -98139,6 +98172,10 @@ export type CustomElementsSolidJs = {
    * selected after. It sends no event, as the native method sends none.
    * - `select() => void`: Selects everything in the field.
    * - `focus(options?: FocusOptions) => void`: Moves focus to the control, as focusing a native control does.
+   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
+   * not. The control shows no message for it: `reportValidity()` does that.
+   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
+   * form's `checkValidity()`, as connecting does for the form it starts in.
    * - `formDisabledCallback(disabled: boolean) => void`: Called by the browser when an ancestor fieldset is disabled or enabled.
    *
    * **The argument is the effective state, and taking it whole is what latched
@@ -98172,14 +98209,10 @@ export type CustomElementsSolidJs = {
    * the fieldset's hold is not recorded. There is no callback to learn it from
    * and reading `:disabled` here would answer about the attribute we are in the
    * middle of removing.
-   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
-   * not. The control shows no message for it: `reportValidity()` does that.
    * - `reportValidity() => boolean`: Returns whether the control is valid, and when it is not, fires `invalid`
    * and shows the browser's message at the control.
    * - `setCustomValidity(message: string) => void`: Marks the control invalid with `message`, or clears that with an empty
    * string, as on a native control. The form does not submit while it is set.
-   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
-   * form's `checkValidity()`, as connecting does for the form it starts in.
    *
    * ## CSS Custom Properties
    *
@@ -98509,6 +98542,10 @@ export type CustomElementsSolidJs = {
    * Falling back to what the markup declared rather than to empty, because
    * a restore with no state is a form the browser has nothing recorded for,
    * which is the same situation as a fresh one.
+   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
+   * not. The control shows no message for it: `reportValidity()` does that.
+   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
+   * form's `checkValidity()`, as connecting does for the form it starts in.
    * - `formDisabledCallback(disabled: boolean) => void`: Called by the browser when an ancestor fieldset is disabled or enabled.
    *
    * **The argument is the effective state, and taking it whole is what latched
@@ -98542,14 +98579,10 @@ export type CustomElementsSolidJs = {
    * the fieldset's hold is not recorded. There is no callback to learn it from
    * and reading `:disabled` here would answer about the attribute we are in the
    * middle of removing.
-   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
-   * not. The control shows no message for it: `reportValidity()` does that.
    * - `reportValidity() => boolean`: Returns whether the control is valid, and when it is not, fires `invalid`
    * and shows the browser's message at the control.
    * - `setCustomValidity(message: string) => void`: Marks the control invalid with `message`, or clears that with an empty
    * string, as on a native control. The form does not submit while it is set.
-   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
-   * form's `checkValidity()`, as connecting does for the form it starts in.
    *
    * ## CSS Custom Properties
    *
@@ -98971,6 +99004,10 @@ export type CustomElementsSolidJs = {
    * calls this again afterwards. The guard below makes the early call harmless
    * rather than wrong, which is why it can be left in.
    * - `focus(options?: FocusOptions) => void`: Moves focus to the control, as focusing a native control does.
+   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
+   * not. The control shows no message for it: `reportValidity()` does that.
+   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
+   * form's `checkValidity()`, as connecting does for the form it starts in.
    * - `formDisabledCallback(disabled: boolean) => void`: Called by the browser when an ancestor fieldset is disabled or enabled.
    *
    * **The argument is the effective state, and taking it whole is what latched
@@ -99004,14 +99041,10 @@ export type CustomElementsSolidJs = {
    * the fieldset's hold is not recorded. There is no callback to learn it from
    * and reading `:disabled` here would answer about the attribute we are in the
    * middle of removing.
-   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
-   * not. The control shows no message for it: `reportValidity()` does that.
    * - `reportValidity() => boolean`: Returns whether the control is valid, and when it is not, fires `invalid`
    * and shows the browser's message at the control.
    * - `setCustomValidity(message: string) => void`: Marks the control invalid with `message`, or clears that with an empty
    * string, as on a native control. The form does not submit while it is set.
-   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
-   * form's `checkValidity()`, as connecting does for the form it starts in.
    *
    * ## CSS Custom Properties
    *
@@ -99807,6 +99840,10 @@ export type CustomElementsSolidJs = {
    * Falling back to what the markup declared rather than to empty, because
    * a restore with no state is a form the browser has nothing recorded for,
    * which is the same situation as a fresh one.
+   * - `checkValidity() => boolean`: Returns whether the control is valid, and fires `invalid` on it when it is
+   * not. The control shows no message for it: `reportValidity()` does that.
+   * - `formAssociatedCallback(form: HTMLFormElement | null) => void`: Called by the browser when the control's form changes: watches the new
+   * form's `checkValidity()`, as connecting does for the form it starts in.
    * - `formDisabledCallback(disabled: boolean) => void`: Called by the browser when an ancestor fieldset is disabled or enabled.
    *
    * **The argument is the effective state, and taking it whole is what latched
@@ -99840,15 +99877,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
    *
@@ -102049,6 +102082,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.
    *
@@ -102071,13 +102110,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