@fusion.dev/helix-headless 0.49.1 → 0.51.0

package/dist/color-picker/root/color-picker-root.d.ts

@@ -25,7 +25,7 @@ declare const HelixHeadlessColorPicker_base: (new (...args: any[]) => import("@f
  * model once.
  *
  * @since 0.1.0
- * @status experimental
+ * @status stable
  * @category forms
  * @aliases Color, ColorArea, Swatch picker
  * @documentation https://fusion.dev/helix/components/color-picker
@@ -147,6 +147,12 @@ export declare class HelixHeadlessColorPicker extends HelixHeadlessColorPicker_b
      * value is requested. Gating only the request would leave the square under
      * the reader's pointer and the value where it was, which is a control that
      * refuses and looks like it accepted.
+     *
+     * **Two controls are refused whole rather than at either seam**, because
+     * both do something before they ask. The syntax toggle rewrites the value, so
+     * letting it move would show `rgb` over a hex it is no longer allowed to
+     * restate. The eyedropper clears the screen and runs a system sampler, so
+     * letting it open would take a color from the reader and drop it.
      */
     readOnly: boolean;
     /**

package/dist/color-picker/root/color-picker-root.js

@@ -68,6 +68,9 @@ let HelixHeadlessColorPicker = class HelixHeadlessColorPicker extends MixinContr
             }
         };
         this.handleEyeDropper = async () => {
+            if (this.readOnly) {
+                return;
+            }
             const Dropper = globalThis.EyeDropper;
             if (!Dropper) {
                 return;

package/dist/rating/root/rating-root.d.ts

@@ -19,7 +19,7 @@ declare const HelixHeadlessRating_base: (new (...args: any[]) => import("@fusion
  * input, and it is announced as one.
  *
  * @since 0.1.0
- * @status experimental
+ * @status stable
  * @category forms
  * @aliases Stars, Score, Review score
  * @documentation https://fusion.dev/helix/components/rating

package/dist/splitter/root/splitter-root.d.ts

@@ -41,8 +41,8 @@ import { type PropertyValues, type TemplateResult } from 'lit';
  * @slot end - The pane after it.
  * @slot start - The pane before the divider.
  *
- * @event {HelixBeforeCollapseEvent} helix-before-collapse - Fired before a pane shuts or reopens, and only where the position it is derived from stood. Cancelable: refusing it leaves the pane as it was and the divider where the gesture put it.
- * @event {HelixBeforeResizeEvent} helix-before-resize - Fired before the divider settles, and only where the gesture moved it: a press that moved nothing, a drag that came back, an arrow with nowhere left to go and a corner that moved the other divider are all silent on this one. Cancelable: refusing it takes the whole of where the gesture ended, so no collapse follows from it either. A drag has already drawn itself by then and holds where it was dropped until the consumer assigns their own.
+ * @event {HelixBeforeCollapseEvent} helix-before-collapse - Fired before a pane shuts or reopens, whether or not the resize that reached it was allowed, and carrying its own position: a shut pane sits at `collapsed-size` rather than at the number the resize named. Cancelable: refusing it leaves the pane as it was and the divider where the gesture put it.
+ * @event {HelixBeforeResizeEvent} helix-before-resize - Fired before the divider settles, and only where the gesture moved it: a press that moved nothing, a drag that came back, an arrow with nowhere left to go and a corner that moved the other divider are all silent on this one. Cancelable: refusing it takes the position and leaves the rest of the gesture, so a collapse the gesture reached is still announced and still yours to refuse. A drag has already drawn itself by then and holds where it was dropped until the consumer assigns their own.
  *
  * @csspart corner - The handle where two dividers cross, added on the client.
  * @csspart end - The box holding the second.
@@ -331,21 +331,36 @@ export declare class HelixHeadlessSplitter extends HelixElement {
      * Through the audited path, so a consumer who owns `position` is told what was
      * asked for and decides, and one who does not has already had it applied.
      *
-     * **The second announcement is conditional on the first, because it is derived
-     * from it.** `shutAt` reads the position the gesture ended on, so a refused
-     * `helix-before-resize` leaves a collapse computed from a number that was
-     * refused. Announced anyway, the refusal produced the outcome it was refusing:
-     * measured on a divider at 40 with a listener calling `preventDefault`, Home
-     * left `position` reporting 0 and `collapsed` reporting `start`, because the
-     * collapse applied and `position` reads the sliver once a pane is shut. The
-     * return of the first request is what says so, and it was being dropped: a
-     * cancelable event dispatched as a bare statement with nothing reading the
-     * answer, which is the shape the navigation cohort named on `Outline` and left.
+     * **A refused resize ends the resize and not the gesture.** `shutAt` reads the
+     * position the gesture ended on, so the collapse is computed from a number the
+     * consumer may have declined, and the reading this replaces was that the two
+     * are therefore one decision: refuse the first and the second cannot stand.
+     * That is a reasonable thing to believe about a splitter nobody else owns, and
+     * it takes "no" to mean the gesture is over. What it misses is that a consumer
+     * who owns the position refuses in order to *take* the decision, not to end
+     * it. The sandbox two folders away refuses every `helix-before-resize` from
+     * the splitter inside it, re-announces the same move in its own vocabulary and
+     * writes the answer back through `position`, which is what makes it the single
+     * decision point; returning on its refusal left `panel-collapsed-size` inert
+     * there, the shipped `with-a-panel` example measuring a 0px panel against the
+     * 36 its summary promises. So the collapse is reached either way and is
+     * refused, or not, on its own.
+     *
+     * **Which is honest because the collapse carries its own position.** A shut
+     * pane sits at `collapsed-size`, which is where `position` reads it from once
+     * `collapsed` is set, and never at the number the resize named: refuse a drag
+     * to 100 on a splitter with `collapsed-size="10"`, allow the collapse, and the
+     * divider is at 90. Nothing writes the refused number either, `requestChange`
+     * applying nothing when it is refused and the collapse below writing the open
+     * position back over whatever a drag had already drawn, so a consumer who says
+     * no to the position and yes to the collapse gets the pane shut and keeps the
+     * number they had to reopen to. The two coincide only where `collapsed-size`
+     * is zero, and the states differ even there: a shut pane knows where to open
+     * back to and a divider parked at the edge does not.
      *
      * Refusing the collapse alone still leaves the resize, which is the other way
      * round and is coherent: the divider goes where the drag put it and the pane
-     * is not declared shut. What a consumer cannot have is a pane that collapses
-     * out from under a position they said no to.
+     * is not declared shut.
      *
      * **A gesture that moved nothing announces nothing, and this is the one place
      * that can say so.** A change carrying the position the divider already had

package/dist/splitter/root/splitter-root.js

@@ -305,7 +305,7 @@ let HelixHeadlessSplitter = HelixHeadlessSplitter_1 = class HelixHeadlessSplitte
         if (wanted === began && shut === this.collapsed) {
             return;
         }
-        const moved = requestChange({
+        requestChange({
             apply: (value) => {
                 const previous = this.position;
                 this.positionState = value;
@@ -315,9 +315,6 @@ let HelixHeadlessSplitter = HelixHeadlessSplitter_1 = class HelixHeadlessSplitte
             host: this,
             next: wanted,
         });
-        if (!moved) {
-            return;
-        }
         if (shut !== this.collapsed) {
             requestChange({
                 apply: (value) => {

package/dist/time-picker/root/time-picker-root.d.ts

@@ -57,7 +57,7 @@ declare const HelixHeadlessTimePicker_base: (new (...args: any[]) => import("@fu
  * wheels, a wheel being a listbox like the list is.
  *
  * @since 0.1.0
- * @status experimental
+ * @status stable
  * @category forms
  * @aliases Time, TimeList
  * @documentation https://fusion.dev/helix/components/time-picker

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@fusion.dev/helix-headless",
   "description": "Headless component tier. Structure, accessibility, state, and form participation. No styling.",
-  "version": "0.49.1",
+  "version": "0.51.0",
   "license": "MIT",
   "author": "Ross Sheppard <ross.sheppard@fusion.dev>",
   "repository": {
@@ -46,14 +46,14 @@
   },
   "bugs": "https://github.com/project-fusion/fusion/issues",
   "dependencies": {
-    "@fusion.dev/helix-core": "0.49.1",
-    "@fusion.dev/helix-icons": "0.49.1",
+    "@fusion.dev/helix-core": "0.51.0",
+    "@fusion.dev/helix-icons": "0.51.0",
     "uqr": "^0.1.3"
   },
   "devDependencies": {
     "@custom-elements-manifest/analyzer": "^0.11.0",
-    "@fusion.dev/helix-cem": "0.49.1",
-    "@fusion.dev/helix-testing": "0.49.1",
+    "@fusion.dev/helix-cem": "0.51.0",
+    "@fusion.dev/helix-testing": "0.51.0",
     "@fusion.dev/scripts": "0.0.0-dev",
     "@happy-dom/global-registrator": "^20.0.0",
     "@lit-labs/ssr": "^4.1.0",

package/types/jsx.d.ts

@@ -1861,6 +1861,29 @@ attribute is the one answer to how wide a pane is.
 A value the track cannot honor is taken to the nearest one it can, by
 `across`, and both tiers read that rather than this.
 
+**`auto` fits as many as the track can hold**, at `--carousel-slide-min`
+apiece, and nothing is written onto the track: the count is the sheet's,
+and the sheet's alone, because it is the one number here CSS can work out
+for itself. Everything it takes is a length the sheet already has, so the
+panes are laid out at their final width by the first rule that runs, on a
+server's markup as on the client's, and no script is waited on. That is the
+whole reason a declared count was ever the only option: a carousel that
+asks how wide its container is can only ask on the client, so the panes go
+down at one width and move to another when the answer arrives. Written
+inline the count would outrank the sheet that computes it, which is why an
+`auto` track is handed nothing. A count stays for the design that calls for
+exactly three.
+
+The styled sheet says how it divides, and the headless `auto` example
+carries the same three lines for a consumer writing their own.
+
+**A value rather than the resting behavior**, which is what the
+responsiveness policy asks of every axis that a box decides: a splitter
+turns on `orientation="auto"` and a plain one does not turn at all. Fitting
+changes what the carousel *does*, since how many are across is how many
+places the track can stop, so a carousel that had not asked for it would
+find its position count moving with the window.
+
 No default, because it reflects. A reflected property with a value writes
 its attribute on upgrade, and the host then carries something a consumer's
 server markup never had, which React reports as a mismatch. The one-across
@@ -1898,6 +1921,29 @@ attribute is the one answer to how wide a pane is.
 A value the track cannot honor is taken to the nearest one it can, by
 `across`, and both tiers read that rather than this.
 
+**`auto` fits as many as the track can hold**, at `--carousel-slide-min`
+apiece, and nothing is written onto the track: the count is the sheet's,
+and the sheet's alone, because it is the one number here CSS can work out
+for itself. Everything it takes is a length the sheet already has, so the
+panes are laid out at their final width by the first rule that runs, on a
+server's markup as on the client's, and no script is waited on. That is the
+whole reason a declared count was ever the only option: a carousel that
+asks how wide its container is can only ask on the client, so the panes go
+down at one width and move to another when the answer arrives. Written
+inline the count would outrank the sheet that computes it, which is why an
+`auto` track is handed nothing. A count stays for the design that calls for
+exactly three.
+
+The styled sheet says how it divides, and the headless `auto` example
+carries the same three lines for a consumer writing their own.
+
+**A value rather than the resting behavior**, which is what the
+responsiveness policy asks of every axis that a box decides: a splitter
+turns on `orientation="auto"` and a plain one does not turn at all. Fitting
+changes what the carousel *does*, since how many are across is how many
+places the track can stop, so a carousel that had not asked for it would
+find its position count moving with the window.
+
 No default, because it reflects. A reflected property with a value writes
 its attribute on upgrade, and the host then carries something a consumer's
 server markup never had, which React reports as a mismatch. The one-across
@@ -2004,6 +2050,29 @@ attribute is the one answer to how wide a pane is.
 A value the track cannot honor is taken to the nearest one it can, by
 `across`, and both tiers read that rather than this.
 
+**`auto` fits as many as the track can hold**, at `--carousel-slide-min`
+apiece, and nothing is written onto the track: the count is the sheet's,
+and the sheet's alone, because it is the one number here CSS can work out
+for itself. Everything it takes is a length the sheet already has, so the
+panes are laid out at their final width by the first rule that runs, on a
+server's markup as on the client's, and no script is waited on. That is the
+whole reason a declared count was ever the only option: a carousel that
+asks how wide its container is can only ask on the client, so the panes go
+down at one width and move to another when the answer arrives. Written
+inline the count would outrank the sheet that computes it, which is why an
+`auto` track is handed nothing. A count stays for the design that calls for
+exactly three.
+
+The styled sheet says how it divides, and the headless `auto` example
+carries the same three lines for a consumer writing their own.
+
+**A value rather than the resting behavior**, which is what the
+responsiveness policy asks of every axis that a box decides: a splitter
+turns on `orientation="auto"` and a plain one does not turn at all. Fitting
+changes what the carousel *does*, since how many are across is how many
+places the track can stop, so a carousel that had not asked for it would
+find its position count moving with the window.
+
 No default, because it reflects. A reflected property with a value writes
 its attribute on upgrade, and the host then carries something a consumer's
 server markup never had, which React reports as a mismatch. The one-across
@@ -2041,6 +2110,29 @@ attribute is the one answer to how wide a pane is.
 A value the track cannot honor is taken to the nearest one it can, by
 `across`, and both tiers read that rather than this.
 
+**`auto` fits as many as the track can hold**, at `--carousel-slide-min`
+apiece, and nothing is written onto the track: the count is the sheet's,
+and the sheet's alone, because it is the one number here CSS can work out
+for itself. Everything it takes is a length the sheet already has, so the
+panes are laid out at their final width by the first rule that runs, on a
+server's markup as on the client's, and no script is waited on. That is the
+whole reason a declared count was ever the only option: a carousel that
+asks how wide its container is can only ask on the client, so the panes go
+down at one width and move to another when the answer arrives. Written
+inline the count would outrank the sheet that computes it, which is why an
+`auto` track is handed nothing. A count stays for the design that calls for
+exactly three.
+
+The styled sheet says how it divides, and the headless `auto` example
+carries the same three lines for a consumer writing their own.
+
+**A value rather than the resting behavior**, which is what the
+responsiveness policy asks of every axis that a box decides: a splitter
+turns on `orientation="auto"` and a plain one does not turn at all. Fitting
+changes what the carousel *does*, since how many are across is how many
+places the track can stop, so a carousel that had not asked for it would
+find its position count moving with the window.
+
 No default, because it reflects. A reflected property with a value writes
 its attribute on upgrade, and the host then carries something a consumer's
 server markup never had, which React reports as a mismatch. The one-across
@@ -3172,7 +3264,13 @@ holds a model beside its value, which Date Picker and Time Picker do not:
 `moved` is the HSB the square is drawn from, and it is written before the
 value is requested. Gating only the request would leave the square under
 the reader's pointer and the value where it was, which is a control that
-refuses and looks like it accepted. */
+refuses and looks like it accepted.
+
+**Two controls are refused whole rather than at either seam**, because
+both do something before they ask. The syntax toggle rewrites the value, so
+letting it move would show `rgb` over a hex it is no longer allowed to
+restate. The eyedropper clears the screen and runs a system sampler, so
+letting it open would take a color from the reader and drop it. */
   readonly?: (HelixHeadlessColorPicker["readOnly"]) | undefined;
   /** Whether the control refuses changes while still submitting its value.
 
@@ -3191,7 +3289,13 @@ holds a model beside its value, which Date Picker and Time Picker do not:
 `moved` is the HSB the square is drawn from, and it is written before the
 value is requested. Gating only the request would leave the square under
 the reader's pointer and the value where it was, which is a control that
-refuses and looks like it accepted. */
+refuses and looks like it accepted.
+
+**Two controls are refused whole rather than at either seam**, because
+both do something before they ask. The syntax toggle rewrites the value, so
+letting it move would show `rgb` over a hex it is no longer allowed to
+restate. The eyedropper clears the screen and runs a system sampler, so
+letting it open would take a color from the reader and drop it. */
   readOnly?: (HelixHeadlessColorPicker["readOnly"]) | undefined;
   /** Whether the form refuses to submit while no color is chosen.
 
@@ -3353,7 +3457,13 @@ holds a model beside its value, which Date Picker and Time Picker do not:
 `moved` is the HSB the square is drawn from, and it is written before the
 value is requested. Gating only the request would leave the square under
 the reader's pointer and the value where it was, which is a control that
-refuses and looks like it accepted. */
+refuses and looks like it accepted.
+
+**Two controls are refused whole rather than at either seam**, because
+both do something before they ask. The syntax toggle rewrites the value, so
+letting it move would show `rgb` over a hex it is no longer allowed to
+restate. The eyedropper clears the screen and runs a system sampler, so
+letting it open would take a color from the reader and drop it. */
   "bool:readonly"?: (HelixHeadlessColorPicker["readOnly"]) | undefined;
   /** Whether the control refuses changes while still submitting its value.
 
@@ -3372,7 +3482,13 @@ holds a model beside its value, which Date Picker and Time Picker do not:
 `moved` is the HSB the square is drawn from, and it is written before the
 value is requested. Gating only the request would leave the square under
 the reader's pointer and the value where it was, which is a control that
-refuses and looks like it accepted. */
+refuses and looks like it accepted.
+
+**Two controls are refused whole rather than at either seam**, because
+both do something before they ask. The syntax toggle rewrites the value, so
+letting it move would show `rgb` over a hex it is no longer allowed to
+restate. The eyedropper clears the screen and runs a system sampler, so
+letting it open would take a color from the reader and drop it. */
   "prop:readOnly"?: (HelixHeadlessColorPicker["readOnly"]) | undefined;
   /** Whether the form refuses to submit while no color is chosen.
 
@@ -13334,11 +13450,11 @@ has an honest answer. */
   /** How far one arrow press moves it, as a percentage. */
   step?: (HelixHeadlessSplitter["step"]) | undefined;
 
-  /** Fired before a pane shuts or reopens, and only where the position it is derived from stood. Cancelable: refusing it leaves the pane as it was and the divider where the gesture put it. */
+  /** Fired before a pane shuts or reopens, whether or not the resize that reached it was allowed, and carrying its own position: a shut pane sits at `collapsed-size` rather than at the number the resize named. Cancelable: refusing it leaves the pane as it was and the divider where the gesture put it. */
   "onhelix-before-collapse"?: ((
     e: HelixHeadlessSplitterHelixBeforeCollapseElementEvent,
   ) => void) | undefined;
-  /** Fired before the divider settles, and only where the gesture moved it: a press that moved nothing, a drag that came back, an arrow with nowhere left to go and a corner that moved the other divider are all silent on this one. Cancelable: refusing it takes the whole of where the gesture ended, so no collapse follows from it either. A drag has already drawn itself by then and holds where it was dropped until the consumer assigns their own. */
+  /** Fired before the divider settles, and only where the gesture moved it: a press that moved nothing, a drag that came back, an arrow with nowhere left to go and a corner that moved the other divider are all silent on this one. Cancelable: refusing it takes the position and leaves the rest of the gesture, so a collapse the gesture reached is still announced and still yours to refuse. A drag has already drawn itself by then and holds where it was dropped until the consumer assigns their own. */
   "onhelix-before-resize"?: ((
     e: HelixHeadlessSplitterHelixBeforeResizeElementEvent,
   ) => void) | undefined;
@@ -13438,11 +13554,11 @@ has an honest answer. */
   "prop:orientation"?: (HelixHeadlessSplitter["orientation"]) | undefined;
   /** How far one arrow press moves it, as a percentage. */
   "prop:step"?: (HelixHeadlessSplitter["step"]) | undefined;
-  /** Fired before a pane shuts or reopens, and only where the position it is derived from stood. Cancelable: refusing it leaves the pane as it was and the divider where the gesture put it. */
+  /** Fired before a pane shuts or reopens, whether or not the resize that reached it was allowed, and carrying its own position: a shut pane sits at `collapsed-size` rather than at the number the resize named. Cancelable: refusing it leaves the pane as it was and the divider where the gesture put it. */
   "on:helix-before-collapse"?: ((
     e: HelixHeadlessSplitterHelixBeforeCollapseElementEvent,
   ) => void) | undefined;
-  /** Fired before the divider settles, and only where the gesture moved it: a press that moved nothing, a drag that came back, an arrow with nowhere left to go and a corner that moved the other divider are all silent on this one. Cancelable: refusing it takes the whole of where the gesture ended, so no collapse follows from it either. A drag has already drawn itself by then and holds where it was dropped until the consumer assigns their own. */
+  /** Fired before the divider settles, and only where the gesture moved it: a press that moved nothing, a drag that came back, an arrow with nowhere left to go and a corner that moved the other divider are all silent on this one. Cancelable: refusing it takes the position and leaves the rest of the gesture, so a collapse the gesture reached is still announced and still yours to refuse. A drag has already drawn itself by then and holds where it was dropped until the consumer assigns their own. */
   "on:helix-before-resize"?: ((
     e: HelixHeadlessSplitterHelixBeforeResizeElementEvent,
   ) => void) | undefined;
@@ -19492,6 +19608,29 @@ export type CustomElements = {
    * A value the track cannot honor is taken to the nearest one it can, by
    * `across`, and both tiers read that rather than this.
    *
+   * **`auto` fits as many as the track can hold**, at `--carousel-slide-min`
+   * apiece, and nothing is written onto the track: the count is the sheet's,
+   * and the sheet's alone, because it is the one number here CSS can work out
+   * for itself. Everything it takes is a length the sheet already has, so the
+   * panes are laid out at their final width by the first rule that runs, on a
+   * server's markup as on the client's, and no script is waited on. That is the
+   * whole reason a declared count was ever the only option: a carousel that
+   * asks how wide its container is can only ask on the client, so the panes go
+   * down at one width and move to another when the answer arrives. Written
+   * inline the count would outrank the sheet that computes it, which is why an
+   * `auto` track is handed nothing. A count stays for the design that calls for
+   * exactly three.
+   *
+   * The styled sheet says how it divides, and the headless `auto` example
+   * carries the same three lines for a consumer writing their own.
+   *
+   * **A value rather than the resting behavior**, which is what the
+   * responsiveness policy asks of every axis that a box decides: a splitter
+   * turns on `orientation="auto"` and a plain one does not turn at all. Fitting
+   * changes what the carousel *does*, since how many are across is how many
+   * places the track can stop, so a carousel that had not asked for it would
+   * find its position count moving with the window.
+   *
    * No default, because it reflects. A reflected property with a value writes
    * its attribute on upgrade, and the host then carries something a consumer's
    * server markup never had, which React reports as a mismatch. The one-across
@@ -19501,7 +19640,11 @@ export type CustomElements = {
    * A window of `perView` slides sliding one at a time over `n` of them stops
    * `n - perView + 1` times, so six slides four across is three: 0 to 3, 1 to 4,
    * 2 to 5. One at minimum, since a carousel showing everything it has still
-   * has the one place to be. (property only) (readonly)
+   * has the one place to be.
+   *
+   * One across until a fitted track has been laid out, which is the same answer
+   * a carousel that has never been told anything gives, and the dots are
+   * withheld rather than counted from it. See `across`. (property only) (readonly)
    * - `slides`: The slides, in light-DOM order. Empty on the server, which has no tree. (property only) (readonly)
    * - `whenSettled`: Resolves a frame after the first update, when transitions are switched on.
    *
@@ -19548,8 +19691,9 @@ export type CustomElements = {
    *
    * - `--carousel-gap`: Space between slides. A sheet sets it and the component measures the run with it. (default: `undefined`)
    * - `--carousel-pane`: The size one pane is laid out at. A sheet sets it and the component measures the run with it. (default: `undefined`)
-   * - `--carousel-per-view`: How many slides go across, written onto the track by the component so a sheet divides the track by the same number the positions are counted from. Read it rather than selecting on `per-view`, which cannot be enumerated without a ceiling. See `perView`. (default: `undefined`)
+   * - `--carousel-per-view`: How many slides go across, written onto the track by the component so a sheet divides the track by the same number the positions are counted from. Read it rather than selecting on `per-view`, which cannot be enumerated without a ceiling. Under `per-view="auto"` the component writes nothing and the sheet declares it instead, so the same name answers in both modes. See `perView`. (default: `undefined`)
    * - `--carousel-run-end`: How far short of a whole pixel the run ends, on the last slide alone, for a sheet to take up as `margin-inline-end`. See `runEnd`. (default: `undefined`)
+   * - `--carousel-slide-min`: The narrowest a slide may be laid out, which is what `per-view="auto"` fits the track with. A length, since the sheet divides by it. Unset is the whole track, which is one across. (default: `undefined`)
    *
    * ## CSS Parts
    *
@@ -20880,6 +21024,12 @@ export type CustomElements = {
    * value is requested. Gating only the request would leave the square under
    * the reader's pointer and the value where it was, which is a control that
    * refuses and looks like it accepted.
+   *
+   * **Two controls are refused whole rather than at either seam**, because
+   * both do something before they ask. The syntax toggle rewrites the value, so
+   * letting it move would show `rgb` over a hex it is no longer allowed to
+   * restate. The eyedropper clears the screen and runs a system sampler, so
+   * letting it open would take a color from the reader and drop it.
    * - `required`: Whether the form refuses to submit while no color is chosen.
    *
    * **A color is exactly as requirable as a date**, which is the comparison
@@ -31145,8 +31295,8 @@ export type CustomElements = {
    *
    * Events that will be emitted by the component.
    *
-   * - `helix-before-collapse`: Fired before a pane shuts or reopens, and only where the position it is derived from stood. Cancelable: refusing it leaves the pane as it was and the divider where the gesture put it.
-   * - `helix-before-resize`: Fired before the divider settles, and only where the gesture moved it: a press that moved nothing, a drag that came back, an arrow with nowhere left to go and a corner that moved the other divider are all silent on this one. Cancelable: refusing it takes the whole of where the gesture ended, so no collapse follows from it either. A drag has already drawn itself by then and holds where it was dropped until the consumer assigns their own.
+   * - `helix-before-collapse`: Fired before a pane shuts or reopens, whether or not the resize that reached it was allowed, and carrying its own position: a shut pane sits at `collapsed-size` rather than at the number the resize named. Cancelable: refusing it leaves the pane as it was and the divider where the gesture put it.
+   * - `helix-before-resize`: Fired before the divider settles, and only where the gesture moved it: a press that moved nothing, a drag that came back, an arrow with nowhere left to go and a corner that moved the other divider are all silent on this one. Cancelable: refusing it takes the position and leaves the rest of the gesture, so a collapse the gesture reached is still announced and still yours to refuse. A drag has already drawn itself by then and holds where it was dropped until the consumer assigns their own.
    *
    * ## Slots
    *
@@ -37373,6 +37523,29 @@ export type CustomElementsSolidJs = {
    * A value the track cannot honor is taken to the nearest one it can, by
    * `across`, and both tiers read that rather than this.
    *
+   * **`auto` fits as many as the track can hold**, at `--carousel-slide-min`
+   * apiece, and nothing is written onto the track: the count is the sheet's,
+   * and the sheet's alone, because it is the one number here CSS can work out
+   * for itself. Everything it takes is a length the sheet already has, so the
+   * panes are laid out at their final width by the first rule that runs, on a
+   * server's markup as on the client's, and no script is waited on. That is the
+   * whole reason a declared count was ever the only option: a carousel that
+   * asks how wide its container is can only ask on the client, so the panes go
+   * down at one width and move to another when the answer arrives. Written
+   * inline the count would outrank the sheet that computes it, which is why an
+   * `auto` track is handed nothing. A count stays for the design that calls for
+   * exactly three.
+   *
+   * The styled sheet says how it divides, and the headless `auto` example
+   * carries the same three lines for a consumer writing their own.
+   *
+   * **A value rather than the resting behavior**, which is what the
+   * responsiveness policy asks of every axis that a box decides: a splitter
+   * turns on `orientation="auto"` and a plain one does not turn at all. Fitting
+   * changes what the carousel *does*, since how many are across is how many
+   * places the track can stop, so a carousel that had not asked for it would
+   * find its position count moving with the window.
+   *
    * No default, because it reflects. A reflected property with a value writes
    * its attribute on upgrade, and the host then carries something a consumer's
    * server markup never had, which React reports as a mismatch. The one-across
@@ -37382,7 +37555,11 @@ export type CustomElementsSolidJs = {
    * A window of `perView` slides sliding one at a time over `n` of them stops
    * `n - perView + 1` times, so six slides four across is three: 0 to 3, 1 to 4,
    * 2 to 5. One at minimum, since a carousel showing everything it has still
-   * has the one place to be. (property only) (readonly)
+   * has the one place to be.
+   *
+   * One across until a fitted track has been laid out, which is the same answer
+   * a carousel that has never been told anything gives, and the dots are
+   * withheld rather than counted from it. See `across`. (property only) (readonly)
    * - `slides`: The slides, in light-DOM order. Empty on the server, which has no tree. (property only) (readonly)
    * - `whenSettled`: Resolves a frame after the first update, when transitions are switched on.
    *
@@ -37429,8 +37606,9 @@ export type CustomElementsSolidJs = {
    *
    * - `--carousel-gap`: Space between slides. A sheet sets it and the component measures the run with it. (default: `undefined`)
    * - `--carousel-pane`: The size one pane is laid out at. A sheet sets it and the component measures the run with it. (default: `undefined`)
-   * - `--carousel-per-view`: How many slides go across, written onto the track by the component so a sheet divides the track by the same number the positions are counted from. Read it rather than selecting on `per-view`, which cannot be enumerated without a ceiling. See `perView`. (default: `undefined`)
+   * - `--carousel-per-view`: How many slides go across, written onto the track by the component so a sheet divides the track by the same number the positions are counted from. Read it rather than selecting on `per-view`, which cannot be enumerated without a ceiling. Under `per-view="auto"` the component writes nothing and the sheet declares it instead, so the same name answers in both modes. See `perView`. (default: `undefined`)
    * - `--carousel-run-end`: How far short of a whole pixel the run ends, on the last slide alone, for a sheet to take up as `margin-inline-end`. See `runEnd`. (default: `undefined`)
+   * - `--carousel-slide-min`: The narrowest a slide may be laid out, which is what `per-view="auto"` fits the track with. A length, since the sheet divides by it. Unset is the whole track, which is one across. (default: `undefined`)
    *
    * ## CSS Parts
    *
@@ -38780,6 +38958,12 @@ export type CustomElementsSolidJs = {
    * value is requested. Gating only the request would leave the square under
    * the reader's pointer and the value where it was, which is a control that
    * refuses and looks like it accepted.
+   *
+   * **Two controls are refused whole rather than at either seam**, because
+   * both do something before they ask. The syntax toggle rewrites the value, so
+   * letting it move would show `rgb` over a hex it is no longer allowed to
+   * restate. The eyedropper clears the screen and runs a system sampler, so
+   * letting it open would take a color from the reader and drop it.
    * - `required`: Whether the form refuses to submit while no color is chosen.
    *
    * **A color is exactly as requirable as a date**, which is the comparison
@@ -49193,8 +49377,8 @@ export type CustomElementsSolidJs = {
    *
    * Events that will be emitted by the component.
    *
-   * - `helix-before-collapse`: Fired before a pane shuts or reopens, and only where the position it is derived from stood. Cancelable: refusing it leaves the pane as it was and the divider where the gesture put it.
-   * - `helix-before-resize`: Fired before the divider settles, and only where the gesture moved it: a press that moved nothing, a drag that came back, an arrow with nowhere left to go and a corner that moved the other divider are all silent on this one. Cancelable: refusing it takes the whole of where the gesture ended, so no collapse follows from it either. A drag has already drawn itself by then and holds where it was dropped until the consumer assigns their own.
+   * - `helix-before-collapse`: Fired before a pane shuts or reopens, whether or not the resize that reached it was allowed, and carrying its own position: a shut pane sits at `collapsed-size` rather than at the number the resize named. Cancelable: refusing it leaves the pane as it was and the divider where the gesture put it.
+   * - `helix-before-resize`: Fired before the divider settles, and only where the gesture moved it: a press that moved nothing, a drag that came back, an arrow with nowhere left to go and a corner that moved the other divider are all silent on this one. Cancelable: refusing it takes the position and leaves the rest of the gesture, so a collapse the gesture reached is still announced and still yours to refuse. A drag has already drawn itself by then and holds where it was dropped until the consumer assigns their own.
    *
    * ## Slots
    *
@@ -53615,10 +53799,12 @@ export type CustomCssProperties = {
   "--carousel-gap"?: (string) | undefined;
   /** The size one pane is laid out at. A sheet sets it and the component measures the run with it. */
   "--carousel-pane"?: (string) | undefined;
-  /** How many slides go across, written onto the track by the component so a sheet divides the track by the same number the positions are counted from. Read it rather than selecting on `per-view`, which cannot be enumerated without a ceiling. See `perView`. */
+  /** How many slides go across, written onto the track by the component so a sheet divides the track by the same number the positions are counted from. Read it rather than selecting on `per-view`, which cannot be enumerated without a ceiling. Under `per-view="auto"` the component writes nothing and the sheet declares it instead, so the same name answers in both modes. See `perView`. */
   "--carousel-per-view"?: (string) | undefined;
   /** How far short of a whole pixel the run ends, on the last slide alone, for a sheet to take up as `margin-inline-end`. See `runEnd`. */
   "--carousel-run-end"?: (string) | undefined;
+  /** The narrowest a slide may be laid out, which is what `per-view="auto"` fits the track with. A length, since the sheet divides by it. Unset is the whole track, which is one across. */
+  "--carousel-slide-min"?: (string) | undefined;
   /** The chosen color, to paint over the transparency check. */
   "--color-input-swatch"?: (string) | undefined;
   /** The chosen brightness, 0 to 100, as a percentage. */