@fusion.dev/helix 0.49.1 → 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",
@@ -122147,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.1",
+  "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.1",
-    "@fusion.dev/helix-headless": "0.49.1",
-    "@fusion.dev/helix-styles": "0.49.1"
+    "@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.1",
-    "@fusion.dev/helix-testing": "0.49.1",
+    "@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.
 
@@ -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
@@ -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

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.