@fusion.dev/helix 0.49.0 → 0.50.0

package/custom-elements.json

@@ -5185,7 +5185,7 @@
           "helix": {
             "category": "media",
             "since": "0.1.0",
-            "status": "experimental",
+            "status": "stable",
             "documentation": "https://fusion.dev/helix/components/aura",
             "aliases": [
               "Backdrop",
@@ -24911,7 +24911,7 @@
                 "text": "boolean"
               },
               "default": "false",
-              "description": "Whether the control refuses changes while still submitting its value.\n\n**Enforced by refusing every request in one place**, which is the seam this\ncomponent already has: `requestValue` is what every path here comes through,\nand gating it once is what stops the next call site from being written\nwithout the check.\n\nNot `disabled`, which is the confusion worth naming: a disabled control\nsubmits nothing and leaves the tab order, and a read-only one submits its\nvalue and stays reachable, which is what a form showing a color somebody\nelse set needs.\n\n**One gate is not enough here, and the second is `move`.** This picker\nholds a model beside its value, which Date Picker and Time Picker do not:\n`moved` is the HSB the square is drawn from, and it is written before the\nvalue is requested. Gating only the request would leave the square under\nthe reader's pointer and the value where it was, which is a control that\nrefuses and looks like it accepted.",
+              "description": "Whether the control refuses changes while still submitting its value.\n\n**Enforced by refusing every request in one place**, which is the seam this\ncomponent already has: `requestValue` is what every path here comes through,\nand gating it once is what stops the next call site from being written\nwithout the check.\n\nNot `disabled`, which is the confusion worth naming: a disabled control\nsubmits nothing and leaves the tab order, and a read-only one submits its\nvalue and stays reachable, which is what a form showing a color somebody\nelse set needs.\n\n**One gate is not enough here, and the second is `move`.** This picker\nholds a model beside its value, which Date Picker and Time Picker do not:\n`moved` is the HSB the square is drawn from, and it is written before the\nvalue is requested. Gating only the request would leave the square under\nthe reader's pointer and the value where it was, which is a control that\nrefuses and looks like it accepted.\n\n**Two controls are refused whole rather than at either seam**, because\nboth do something before they ask. The syntax toggle rewrites the value, so\nletting it move would show `rgb` over a hex it is no longer allowed to\nrestate. The eyedropper clears the screen and runs a system sampler, so\nletting it open would take a color from the reader and drop it.",
               "attribute": "readonly",
               "reflects": true,
               "inheritedFrom": {
@@ -25796,7 +25796,7 @@
           "helix": {
             "category": "forms",
             "since": "0.1.0",
-            "status": "experimental",
+            "status": "stable",
             "documentation": "https://fusion.dev/helix/components/color-picker",
             "aliases": [
               "Color",
@@ -25968,7 +25968,7 @@
                 "text": "boolean"
               },
               "default": "false",
-              "description": "Whether the control refuses changes while still submitting its value.\n\n**Enforced by refusing every request in one place**, which is the seam this\ncomponent already has: `requestValue` is what every path here comes through,\nand gating it once is what stops the next call site from being written\nwithout the check.\n\nNot `disabled`, which is the confusion worth naming: a disabled control\nsubmits nothing and leaves the tab order, and a read-only one submits its\nvalue and stays reachable, which is what a form showing a color somebody\nelse set needs.\n\n**One gate is not enough here, and the second is `move`.** This picker\nholds a model beside its value, which Date Picker and Time Picker do not:\n`moved` is the HSB the square is drawn from, and it is written before the\nvalue is requested. Gating only the request would leave the square under\nthe reader's pointer and the value where it was, which is a control that\nrefuses and looks like it accepted.",
+              "description": "Whether the control refuses changes while still submitting its value.\n\n**Enforced by refusing every request in one place**, which is the seam this\ncomponent already has: `requestValue` is what every path here comes through,\nand gating it once is what stops the next call site from being written\nwithout the check.\n\nNot `disabled`, which is the confusion worth naming: a disabled control\nsubmits nothing and leaves the tab order, and a read-only one submits its\nvalue and stays reachable, which is what a form showing a color somebody\nelse set needs.\n\n**One gate is not enough here, and the second is `move`.** This picker\nholds a model beside its value, which Date Picker and Time Picker do not:\n`moved` is the HSB the square is drawn from, and it is written before the\nvalue is requested. Gating only the request would leave the square under\nthe reader's pointer and the value where it was, which is a control that\nrefuses and looks like it accepted.\n\n**Two controls are refused whole rather than at either seam**, because\nboth do something before they ask. The syntax toggle rewrites the value, so\nletting it move would show `rgb` over a hex it is no longer allowed to\nrestate. The eyedropper clears the screen and runs a system sampler, so\nletting it open would take a color from the reader and drop it.",
               "fieldName": "readOnly",
               "inheritedFrom": {
                 "name": "HelixHeadlessColorPicker",
@@ -92429,7 +92429,7 @@
           "helix": {
             "category": "forms",
             "since": "0.1.0",
-            "status": "experimental",
+            "status": "stable",
             "documentation": "https://fusion.dev/helix/components/rating",
             "aliases": [
               "Stars",
@@ -105752,6 +105752,20 @@
                 "module": "src/splitter/root/splitter-root.ts"
               }
             },
+            {
+              "kind": "field",
+              "name": "began",
+              "type": {
+                "text": "number | undefined"
+              },
+              "privacy": "private",
+              "default": "undefined",
+              "description": "Where the divider was when the gesture now under way began.\n\nTaken on the press, read once by `settle` and cleared there. `undefined`\nbetween gestures and for every discrete path, where nothing has been\napplied yet and so the position it has *is* the position it began at.\n\nBeside `opened` rather than folded into it: that one is `undefined` for a\npane that starts shut, which is a different question and a real answer.",
+              "inheritedFrom": {
+                "name": "HelixHeadlessSplitter",
+                "module": "src/splitter/root/splitter-root.ts"
+              }
+            },
             {
               "kind": "field",
               "name": "reached",
@@ -106062,7 +106076,7 @@
                   }
                 }
               ],
-              "description": "Says the arrangement has settled, so a consumer can keep it.\n\nThrough the audited path, so a consumer who owns `position` is told what was\nasked for and decides, and one who does not has already had it applied.\n\n**The second announcement is conditional on the first, because it is derived\nfrom it.** `shutAt` reads the position the gesture ended on, so a refused\n`helix-before-resize` leaves a collapse computed from a number that was\nrefused. Announced anyway, the refusal produced the outcome it was refusing:\nmeasured on a divider at 40 with a listener calling `preventDefault`, Home\nleft `position` reporting 0 and `collapsed` reporting `start`, because the\ncollapse applied and `position` reads the sliver once a pane is shut. The\nreturn of the first request is what says so, and it was being dropped: a\ncancelable event dispatched as a bare statement with nothing reading the\nanswer, which is the shape the navigation cohort named on `Outline` and left.\n\nRefusing the collapse alone still leaves the resize, which is the other way\nround and is coherent: the divider goes where the drag put it and the pane\nis not declared shut. What a consumer cannot have is a pane that collapses\nout from under a position they said no to.",
+              "description": "Says the arrangement has settled, so a consumer can keep it.\n\nThrough the audited path, so a consumer who owns `position` is told what was\nasked for and decides, and one who does not has already had it applied.\n\n**The second announcement is conditional on the first, because it is derived\nfrom it.** `shutAt` reads the position the gesture ended on, so a refused\n`helix-before-resize` leaves a collapse computed from a number that was\nrefused. Announced anyway, the refusal produced the outcome it was refusing:\nmeasured on a divider at 40 with a listener calling `preventDefault`, Home\nleft `position` reporting 0 and `collapsed` reporting `start`, because the\ncollapse applied and `position` reads the sliver once a pane is shut. The\nreturn of the first request is what says so, and it was being dropped: a\ncancelable event dispatched as a bare statement with nothing reading the\nanswer, which is the shape the navigation cohort named on `Outline` and left.\n\nRefusing the collapse alone still leaves the resize, which is the other way\nround and is coherent: the divider goes where the drag put it and the pane\nis not declared shut. What a consumer cannot have is a pane that collapses\nout from under a position they said no to.\n\n**A gesture that moved nothing announces nothing, and this is the one place\nthat can say so.** A change carrying the position the divider already had\nrewrites a consumer's stored value from a gesture that moved nothing:\nharmless where the value round-trips exactly, and not where it does not,\nwhich is any consumer storing pixels and dividing by a box. The separator's\n`pointerup` held that as an early return of its own and was the only door\nwith one. There are five: the separator's pointer and arrows, the corner's\npointer and arrows, and a double click through `reset`, and `moveTo` is a\nsixth a consumer can open. Measured in Chromium 17 Sep 2026 on the built\nbundle, every door but the guarded one announced a move of zero: a corner\npress with nothing between announced on both splitters, `Home` on a divider\nalready at its minimum announced, and a double click on one already at its\ndefault announced.\n\n**Measured against where the gesture began, and not against `position`.**\n`move` applies as it goes, so by the time a drag settles the position is\nalready the number about to be announced, and comparing those two would\nsilence every drag there is. `began` is the press; a discrete path takes\nnone and compares against the position, which for it is the same thing.\n\n**Per divider rather than per gesture, which is the corner's question.** The\ncorner drives two at once, so \"moved nothing\" cannot mean \"neither moved\":\na drag along one axis moves one of them, and the other would be announcing\na number nobody asked to change. Each settles on its own and guards on its\nown, so the one that moved still announces while the one that did not stays\nquiet. That is also why the guard cannot live in `handleCornerUp`, which\nonly ever sees the pair.\n\n**The collapse counts as movement, because a refusal can leave the two\ndisagreeing.** A consumer who refuses `helix-before-collapse` has a pane at\nthe edge that is not declared shut, and a guard reading the position alone\nwould then never offer the collapse again: `Home` is already at the\nminimum, so every later press is a move of zero.",
               "inheritedFrom": {
                 "name": "HelixHeadlessSplitter",
                 "module": "src/splitter/root/splitter-root.ts"
@@ -106877,7 +106891,7 @@
               "type": {
                 "text": "HelixBeforeResizeEvent"
               },
-              "description": "Fired before the divider settles. 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.",
+              "description": "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.",
               "name": "helix-before-resize",
               "reactProp": "onhelix-before-resize",
               "inheritedFrom": {
@@ -122133,7 +122147,7 @@
           "helix": {
             "category": "forms",
             "since": "0.1.0",
-            "status": "experimental",
+            "status": "stable",
             "documentation": "https://fusion.dev/helix/components/time-picker",
             "aliases": [
               "Time",

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

@@ -34,7 +34,7 @@ import type { CSSResultGroup, PropertyValues, TemplateResult } from 'lit';
  * consumer could restyle and nothing for a headless twin to hold.
  *
  * @since 0.1.0
- * @status experimental
+ * @status stable
  * @category media
  * @aliases Backdrop, Background, Atmosphere, Gradient
  * @documentation https://fusion.dev/helix/components/aura

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

@@ -31,7 +31,7 @@ import '../../slider/index.js';
  * brought its own card would be a card inside a card there.
  *
  * @since 0.1.0
- * @status experimental
+ * @status stable
  * @category forms
  * @aliases Color, ColorArea, Swatch picker
  * @documentation https://fusion.dev/helix/components/color-picker

package/dist/rating/root/rating-root.css.js

@@ -12,7 +12,7 @@ gap: var(--helix-space-2xs);
 [part="field"] {
 align-items: center;
 display: inline-flex;
-gap: var(--rating-gap, var(--helix-space-xs));
+gap: var(--helix-space-xs);
 }
 
 [part="marks"] {

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

@@ -8,7 +8,7 @@ import type { CSSResultGroup } from 'lit';
  * Everything about what the score is and how it is chosen is the base class.
  *
  * @since 0.1.0
- * @status experimental
+ * @status stable
  * @category forms
  * @aliases Stars, Score, Review score
  * @documentation https://fusion.dev/helix/components/rating

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

@@ -16,7 +16,7 @@ import '../../option/index.js';
  * card would be a card inside a card there.
  *
  * @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",
   "description": "Styled component tier. Extends the headless tier with token-driven presentation.",
-  "version": "0.49.0",
+  "version": "0.50.0",
   "license": "MIT",
   "author": "Ross Sheppard <ross.sheppard@fusion.dev>",
   "repository": {
@@ -47,14 +47,14 @@
   },
   "bugs": "https://github.com/project-fusion/fusion/issues",
   "dependencies": {
-    "@fusion.dev/helix-core": "0.49.0",
-    "@fusion.dev/helix-headless": "0.49.0",
-    "@fusion.dev/helix-styles": "0.49.0"
+    "@fusion.dev/helix-core": "0.50.0",
+    "@fusion.dev/helix-headless": "0.50.0",
+    "@fusion.dev/helix-styles": "0.50.0"
   },
   "devDependencies": {
     "@custom-elements-manifest/analyzer": "^0.11.0",
-    "@fusion.dev/helix-cem": "0.49.0",
-    "@fusion.dev/helix-testing": "0.49.0",
+    "@fusion.dev/helix-cem": "0.50.0",
+    "@fusion.dev/helix-testing": "0.50.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

@@ -4348,7 +4348,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?: (HelixColorPicker["readOnly"]) | undefined;
   /** Whether the control refuses changes while still submitting its value.
 
@@ -4367,7 +4373,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?: (HelixColorPicker["readOnly"]) | undefined;
   /** Whether the form refuses to submit while no color is chosen.
 
@@ -4529,7 +4541,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"?: (HelixColorPicker["readOnly"]) | undefined;
   /** Whether the control refuses changes while still submitting its value.
 
@@ -4548,7 +4566,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"?: (HelixColorPicker["readOnly"]) | undefined;
   /** Whether the form refuses to submit while no color is chosen.
 
@@ -16043,7 +16067,7 @@ has an honest answer. */
   "onhelix-before-collapse"?: ((
     e: HelixSplitterHelixBeforeCollapseElementEvent,
   ) => void) | undefined;
-  /** Fired before the divider settles. 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 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. */
   "onhelix-before-resize"?: ((
     e: HelixSplitterHelixBeforeResizeElementEvent,
   ) => void) | undefined;
@@ -16163,7 +16187,7 @@ has an honest answer. */
   "on:helix-before-collapse"?: ((
     e: HelixSplitterHelixBeforeCollapseElementEvent,
   ) => void) | undefined;
-  /** Fired before the divider settles. 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 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. */
   "on:helix-before-resize"?: ((
     e: HelixSplitterHelixBeforeResizeElementEvent,
   ) => void) | undefined;
@@ -24385,6 +24409,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
@@ -35625,7 +35655,7 @@ 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. 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-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.
    *
    * ## Slots
    *
@@ -43852,6 +43882,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
@@ -55326,7 +55362,7 @@ 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. 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-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.
    *
    * ## Slots
    *

package/types/vue.d.ts

@@ -2275,7 +2275,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?: (HelixColorPicker["readOnly"]) | undefined;
   /** Whether the control refuses changes while still submitting its value.
 
@@ -2294,7 +2300,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?: (HelixColorPicker["readOnly"]) | undefined;
   /** Whether the form refuses to submit while no color is chosen.
 
@@ -8277,7 +8289,7 @@ has an honest answer. */
 export type HelixSplitterVueEvents = {
   /** 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-collapse": HelixSplitterHelixBeforeCollapseElementEvent;
-  /** Fired before the divider settles. 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 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-resize": HelixSplitterHelixBeforeResizeElementEvent;
 };