@fusion.dev/helix 0.42.0 → 0.43.0

package/custom-elements.json

@@ -36776,7 +36776,7 @@
       "declarations": [
         {
           "kind": "class",
-          "description": "Six week rows always, so the grid keeps one height and a month change does\nnot move whatever sits beneath it.\n\nThe column track is wider than the day, and the day is centered in it. The\ndifference is the space between days, which belongs to the track rather than\nto a `gap`, so a range can paint across the whole track and stay continuous.\n\nDays from the neighboring months stay in place and stay selectable, marked\nquieter rather than hidden, so the first and last weeks are whole and the\ngrid reads as a continuous run of dates.",
+          "description": "Six week rows always, so the grid keeps one height and a month change does\nnot move whatever sits beneath it.\n\nThe column track is wider than the day, and the day is centered in it. The\ndifference is the space between days, which belongs to the track rather than\nto a `gap`, so a range can paint across the whole track and stay continuous.\n\nDays from the neighboring months stay in place, marked quieter rather than\nhidden, so the first and last weeks are whole rows rather than ragged ones.\nThey are filler and take no click, which the pointer says: no hover, and the\ncursor a box that does nothing has. At `months=\"2\"` the same date is a\ntrailing cell in one grid and a real one in the next, so a filler day that\ncould be chosen would put one answer on the page twice.",
           "name": "HelixDatePicker",
           "cssProperties": [
             {
@@ -38075,7 +38075,7 @@
           "helix": {
             "category": "forms",
             "since": "0.1.0",
-            "status": "experimental",
+            "status": "stable",
             "documentation": "https://fusion.dev/helix/components/date-picker",
             "aliases": [
               "Calendar",
@@ -53069,7 +53069,7 @@
           "helix": {
             "category": "typography",
             "since": "0.1.0",
-            "status": "experimental",
+            "status": "stable",
             "documentation": "https://fusion.dev/helix/components/format-date",
             "tier": "styled",
             "group": "FormatDate",
@@ -78526,17 +78526,7 @@
               "type": {
                 "text": "boolean"
               },
-              "description": "Whether the markup declared this one chosen, which is what a reset returns to.\n\n`<option selected>` reflects to `defaultSelected` and `option.selected` is\nlive state that does not reflect, and those are two different facts. This\nelement has one `selected` doing both jobs, so what is captured here is what\nthe markup said at upgrade, before anything could overwrite it: read the\nattribute later and the listbox's own writes answer instead.\n\n**The deeper half is 302 and is not this.** State reflecting under the\ndeclaration's name is the fault `TreeItem` already avoids by mirroring to\n`data-selected`, and four families here still write `selected` back into a\nconsumer's markup. Splitting them means moving what every stylesheet selects\non, which is a change of its own rather than a property being added.",
-              "inheritedFrom": {
-                "name": "HelixHeadlessOption",
-                "module": "src/option/root/option-root.ts"
-              }
-            },
-            {
-              "kind": "field",
-              "name": "seeded",
-              "privacy": "private",
-              "description": "What the markup said, read once at construction for the reason above.",
+              "description": "Whether the markup declared this one chosen, which is what a reset returns to.\n\n`<option selected>` reflects to `defaultSelected` and `option.selected` is\nlive state that does not reflect, and those are two different facts. This\nelement has one `selected` doing both jobs, so the declaration is the\nattribute and the state is the property.\n\n**The attribute, read when it is asked for, and never a snapshot taken in\nthe constructor.** A field initializer runs there, and an element the HTML\nparser created has none of its attributes yet at that moment: measured on\nthis element, on `Radio` and on `Toggle`, `<helix-option value=\"a\"\nselected>` reported `defaultSelected` as `false` both from parsed markup\nand from `createElement` followed by `setAttribute`, which is every way a\nconsumer writes one. The snapshot could only ever be true for an element\nalready in the document when `customElements.define` ran.\n\nNothing overwrites it either, which is what makes reading it late correct\nrather than merely later: `selected` does not reflect, for the reason\n`willUpdate` records, so the listbox's writes never reach the attribute and\nwhat it says is what the markup said.\n\n**The deeper half is not this.** State reflecting under the declaration's\nname is the fault `TreeItem` avoids by mirroring to `data-selected`.\nSplitting them means moving what every stylesheet selects on, which is a\nchange of its own rather than a property being added.",
               "inheritedFrom": {
                 "name": "HelixHeadlessOption",
                 "module": "src/option/root/option-root.ts"
@@ -90017,17 +90007,7 @@
               "type": {
                 "text": "boolean"
               },
-              "description": "Whether the markup declared this one chosen, which is what a reset returns to.\n\n`<option selected>` reflects to `defaultSelected` and `option.selected` is\nlive state that does not reflect, and those are two different facts. This\nelement has one `selected` doing both jobs, so what is captured here is what\nthe markup said at upgrade, before anything could overwrite it: read the\nattribute later and the listbox's own writes answer instead.\n\n**The deeper half is not this.** State reflecting under the declaration's\nname is the fault `TreeItem` avoids by mirroring to `data-selected`.\nSplitting them means moving what every stylesheet selects on, which is a\nchange of its own rather than a property being added.",
-              "inheritedFrom": {
-                "name": "HelixHeadlessRadio",
-                "module": "src/radio/root/radio-root.ts"
-              }
-            },
-            {
-              "kind": "field",
-              "name": "seeded",
-              "privacy": "private",
-              "description": "What the markup said, read once at construction for the reason above.",
+              "description": "Whether the markup declared this one chosen, which is what a reset returns to.\n\n`<option selected>` reflects to `defaultSelected` and `option.selected` is\nlive state that does not reflect, and those are two different facts. This\nelement has one `selected` doing both jobs, so the declaration is the\nattribute and the state is the property.\n\n**The attribute, read when it is asked for, and never a snapshot taken in\nthe constructor.** A field initializer runs there, and an element the HTML\nparser created has none of its attributes yet at that moment: measured on\nthis element, on `Option` and on `Toggle`, `<helix-radio value=\"a\"\nselected>` reported `defaultSelected` as `false` both from parsed markup\nand from `createElement` followed by `setAttribute`, which is every way a\nconsumer writes one. The snapshot could only ever be true for an element\nalready in the document when `customElements.define` ran.\n\nNothing overwrites it either, which is what makes reading it late correct\nrather than merely later: `selected` does not reflect, for the reason\n`willUpdate` records, so the group's writes never reach the attribute and\nwhat it says is what the markup said.\n\n**The deeper half is not this.** State reflecting under the declaration's\nname is the fault `TreeItem` avoids by mirroring to `data-selected`.\nSplitting them means moving what every stylesheet selects on, which is a\nchange of its own rather than a property being added.",
               "inheritedFrom": {
                 "name": "HelixHeadlessRadio",
                 "module": "src/radio/root/radio-root.ts"
@@ -101167,7 +101147,7 @@
               }
             },
             {
-              "description": "Where the filled span starts, as a percentage of the track.",
+              "description": "Where a range's filled span starts, as a fraction of the track, 0 to 1.",
               "name": "--slider-from",
               "inheritedFrom": {
                 "name": "HelixHeadlessSlider",
@@ -101183,7 +101163,7 @@
               }
             },
             {
-              "description": "Where the filled span ends, as a percentage of the track.",
+              "description": "Where a range's filled span ends, as a fraction of the track, 0 to 1.",
               "name": "--slider-to",
               "inheritedFrom": {
                 "name": "HelixHeadlessSlider",
@@ -102356,7 +102336,7 @@
           "helix": {
             "category": "forms",
             "since": "0.1.0",
-            "status": "experimental",
+            "status": "stable",
             "documentation": "https://fusion.dev/helix/components/slider",
             "aliases": [
               "Range",
@@ -124969,6 +124949,22 @@
                 "name": "HelixHeadlessToggleGroup",
                 "module": "src/toggle/group/toggle-group.ts"
               }
+            },
+            {
+              "description": "Whatever sits after the track on its own line, such as a count or a reset.",
+              "name": "end",
+              "inheritedFrom": {
+                "name": "HelixHeadlessToggleGroup",
+                "module": "src/toggle/group/toggle-group.ts"
+              }
+            },
+            {
+              "description": "Whatever sits before the track on its own line, such as an icon or a caption.",
+              "name": "start",
+              "inheritedFrom": {
+                "name": "HelixHeadlessToggleGroup",
+                "module": "src/toggle/group/toggle-group.ts"
+              }
             }
           ],
           "members": [
@@ -125344,6 +125340,21 @@
                 "module": "src/mixins/mixin-field/mixin-field.ts"
               }
             },
+            {
+              "kind": "method",
+              "name": "adopt",
+              "privacy": "private",
+              "return": {
+                "type": {
+                  "text": "void"
+                }
+              },
+              "description": "Takes the markup's own answer where nothing has set a value.\n\n**The case a server renders**, and `Tabs` records the same fault from the\nother side. This element cannot choose on the server, having no children to\ncount, so a consumer whose first paint is right wrote `selected` on the\nitem: that serves `aria-checked=\"true\"`, and `sync` then cleared it one\nframe later, because `value` is `''` and nothing matches it. The shipped\n`disabled` example is exactly that markup, and drew both of its groups with\nnothing chosen.\n\n**Onto `defaultValue`, never onto `value`**, which is the same call\n`Slider` makes about the midpoint it seeds: what the markup declared is a\nfact about the markup, so it is where a reset returns to rather than\nsomething the reader chose. It also makes the group report the answer it is\nshowing, which marking the item alone would not: a `required` group would\notherwise tell a reader a value is missing while they are looking at one.\n\nA written `value` still wins, a declared property being a seed and a\ncorrection, and a group with neither still marks nothing at all.\n\n**The property and never `defaultSelected`, which is the attribute.** React\nassigns a JSX prop as a property where the custom element has one, and\nwrites no attribute at all, so keying on the attribute answers for markup\nand not for JSX. Measured by the parity check on the shipped `disabled`\nexample, whose two syntaxes are the same tree: 192 pixels apart, the HTML\nmarking `List` and the TSX marking nothing. The attribute seeds the\nproperty at upgrade, so reading the property covers both.\n\nRead before `sync` writes to it, which is the only moment it still holds\nwhat the consumer declared: after that it holds this group's answer, and\n`value` is no longer empty, so this returns above.\n\n**Called from `willUpdate` and from the slot, never from `sync`**, which\nruns in `updated`: a reactive property set there schedules a second update,\nand Lit's development build warns about exactly that once per group. From\n`willUpdate` the first render already carries the value, which is the pass\nthat has to be right. `children` is undefined on the server, whose element\nshim carries attributes and no tree, and that is the same guard\n`MixinCollection` records for the same reason.",
+              "inheritedFrom": {
+                "name": "HelixHeadlessToggleGroup",
+                "module": "src/toggle/group/toggle-group.ts"
+              }
+            },
             {
               "kind": "method",
               "name": "sync",
@@ -126057,7 +126068,7 @@
           "summary": "A row of options with the selection marked by a moving indicator.",
           "helix": {
             "since": "0.1.0",
-            "status": "experimental",
+            "status": "stable",
             "documentation": "https://fusion.dev/helix/components/toggle",
             "aliases": [
               "SegmentedControl",
@@ -126215,7 +126226,7 @@
           "name": "HelixToggle",
           "cssParts": [
             {
-              "description": "The button or anchor.",
+              "description": "The radio button.",
               "name": "item",
               "inheritedFrom": {
                 "name": "HelixHeadlessToggle",
@@ -126255,17 +126266,7 @@
               "type": {
                 "text": "boolean"
               },
-              "description": "Whether the markup declared this one chosen, which is what a reset returns to.\n\n`<option selected>` reflects to `defaultSelected` and `option.selected` is\nlive state that does not reflect, and those are two different facts. This\nelement has one `selected` doing both jobs, so what is captured here is what\nthe markup said at upgrade, before anything could overwrite it: read the\nattribute later and the listbox's own writes answer instead.\n\n**The deeper half is not this.** State reflecting under the declaration's\nname is the fault `TreeItem` avoids by mirroring to `data-selected`.\nSplitting them means moving what every stylesheet selects on, which is a\nchange of its own rather than a property being added.",
-              "inheritedFrom": {
-                "name": "HelixHeadlessToggle",
-                "module": "src/toggle/root/toggle-root.ts"
-              }
-            },
-            {
-              "kind": "field",
-              "name": "seeded",
-              "privacy": "private",
-              "description": "What the markup said, read once at construction for the reason above.",
+              "description": "Whether the markup declared this one chosen, which is what a reset returns to.\n\n`<option selected>` reflects to `defaultSelected` and `option.selected` is\nlive state that does not reflect, and those are two different facts. This\nelement has one `selected` doing both jobs, so the declaration is the\nattribute and the state is the property.\n\n**The attribute, read when it is asked for, and never a snapshot taken in\nthe constructor.** A field initializer runs there, and an element the HTML\nparser created has none of its attributes yet at that moment: measured on\nthis element, on `Option` and on `Radio`, `<helix-toggle value=\"light\"\nselected>` reported `defaultSelected` as `false` both from parsed markup\nand from `createElement` followed by `setAttribute`, which is every way a\nconsumer writes one. The snapshot could only ever be true for an element\nalready in the document when `customElements.define` ran.\n\nNothing overwrites it either, which is what makes reading it late correct\nrather than merely later: `selected` does not reflect, for the reason\n`willUpdate` records, so the group's writes never reach the attribute and\nwhat it says is what the markup said.\n\n**The deeper half is not this.** State reflecting under the declaration's\nname is the fault `TreeItem` avoids by mirroring to `data-selected`.\nSplitting them means moving what every stylesheet selects on, which is a\nchange of its own rather than a property being added.",
               "inheritedFrom": {
                 "name": "HelixHeadlessToggle",
                 "module": "src/toggle/root/toggle-root.ts"
@@ -126679,7 +126680,7 @@
           "helix": {
             "category": "actions",
             "since": "0.1.0",
-            "status": "experimental",
+            "status": "stable",
             "documentation": "https://fusion.dev/helix/components/toggle",
             "aliases": [
               "Segment",

package/dist/date-picker/root/date-picker-root.css.js

@@ -116,6 +116,10 @@ box-shadow: inset 0 0 0 var(--helix-border-thin) var(--helix-color-border);
 color: var(--helix-color-foreground-subtle);
 }
 
+[part~="cell"][data-outside] {
+cursor: default;
+}
+
 [part~="cell"]:hover:not([aria-disabled], [data-outside]) [part~="day"] {
 background-color: var(--helix-color-surface-sunken);
 }

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

@@ -11,12 +11,15 @@ import type { CSSResultGroup } from 'lit';
  * difference is the space between days, which belongs to the track rather than
  * to a `gap`, so a range can paint across the whole track and stay continuous.
  *
- * Days from the neighboring months stay in place and stay selectable, marked
- * quieter rather than hidden, so the first and last weeks are whole and the
- * grid reads as a continuous run of dates.
+ * Days from the neighboring months stay in place, marked quieter rather than
+ * hidden, so the first and last weeks are whole rows rather than ragged ones.
+ * They are filler and take no click, which the pointer says: no hover, and the
+ * cursor a box that does nothing has. At `months="2"` the same date is a
+ * trailing cell in one grid and a real one in the next, so a filler day that
+ * could be chosen would put one answer on the page twice.
  *
  * @since 0.1.0
- * @status experimental
+ * @status stable
  * @category forms
  * @aliases Calendar, Date grid, Month view
  * @documentation https://fusion.dev/helix/components/date-picker

package/dist/format-date/root/format-date-root.d.ts

@@ -13,7 +13,7 @@ import type { CSSResultGroup } from 'lit';
  * date is written once and should sit in the text like the text.
  *
  * @since 0.1.0
- * @status experimental
+ * @status stable
  * @category typography
  * @documentation https://fusion.dev/helix/components/format-date
  */

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

@@ -15,7 +15,7 @@ import type { CSSResultGroup } from 'lit';
  * the thumb being dragged.
  *
  * @since 0.1.0
- * @status experimental
+ * @status stable
  * @category forms
  * @aliases Range, Range input
  * @documentation https://fusion.dev/helix/components/slider

package/dist/toggle/group/toggle-group.d.ts

@@ -15,11 +15,13 @@ import type { CSSResultGroup } from 'lit';
  * corner radius, which is worse than the exception.
  *
  * @since 0.1.0
- * @status experimental
+ * @status stable
  * @aliases SegmentedControl, Segmented, Navigation, Switcher
  * @documentation https://fusion.dev/helix/components/toggle
  *
  * @slot - The group's items.
+ * @slot end - Whatever sits after the track on its own line, such as a count or a reset.
+ * @slot start - Whatever sits before the track on its own line, such as an icon or a caption.
  *
  * @csspart indicator - The moving marker behind the selected item.
  *

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

@@ -9,14 +9,14 @@ import type { CSSResultGroup } from 'lit';
  * one fill appearing as another disappears.
  *
  * @since 0.1.0
- * @status experimental
+ * @status stable
  * @category actions
  * @aliases Segment, NavItem, Option
  * @documentation https://fusion.dev/helix/components/toggle
  *
  * @slot - The item's label.
  *
- * @csspart item - The button or anchor.
+ * @csspart item - The radio button.
  */
 export declare class HelixToggle extends HelixHeadlessToggle {
     static styles: CSSResultGroup;

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.42.0",
+  "version": "0.43.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.42.0",
-    "@fusion.dev/helix-headless": "0.42.0",
-    "@fusion.dev/helix-styles": "0.42.0"
+    "@fusion.dev/helix-core": "0.43.0",
+    "@fusion.dev/helix-headless": "0.43.0",
+    "@fusion.dev/helix-styles": "0.43.0"
   },
   "devDependencies": {
     "@custom-elements-manifest/analyzer": "^0.11.0",
-    "@fusion.dev/helix-cem": "0.42.0",
-    "@fusion.dev/helix-testing": "0.42.0",
+    "@fusion.dev/helix-cem": "0.43.0",
+    "@fusion.dev/helix-testing": "0.43.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

@@ -12088,15 +12088,27 @@ Written by the listbox. */
 
 `<option selected>` reflects to `defaultSelected` and `option.selected` is
 live state that does not reflect, and those are two different facts. This
-element has one `selected` doing both jobs, so what is captured here is what
-the markup said at upgrade, before anything could overwrite it: read the
-attribute later and the listbox's own writes answer instead.
-
-**The deeper half is 302 and is not this.** State reflecting under the
-declaration's name is the fault `TreeItem` already avoids by mirroring to
-`data-selected`, and four families here still write `selected` back into a
-consumer's markup. Splitting them means moving what every stylesheet selects
-on, which is a change of its own rather than a property being added. */
+element has one `selected` doing both jobs, so the declaration is the
+attribute and the state is the property.
+
+**The attribute, read when it is asked for, and never a snapshot taken in
+the constructor.** A field initializer runs there, and an element the HTML
+parser created has none of its attributes yet at that moment: measured on
+this element, on `Radio` and on `Toggle`, `<helix-option value="a"
+selected>` reported `defaultSelected` as `false` both from parsed markup
+and from `createElement` followed by `setAttribute`, which is every way a
+consumer writes one. The snapshot could only ever be true for an element
+already in the document when `customElements.define` ran.
+
+Nothing overwrites it either, which is what makes reading it late correct
+rather than merely later: `selected` does not reflect, for the reason
+`willUpdate` records, so the listbox's writes never reach the attribute and
+what it says is what the markup said.
+
+**The deeper half is not this.** State reflecting under the declaration's
+name is the fault `TreeItem` avoids by mirroring to `data-selected`.
+Splitting them means moving what every stylesheet selects on, which is a
+change of its own rather than a property being added. */
   defaultSelected?: (HelixOption["defaultSelected"]) | undefined;
 
   /** Fired when this choice is made. Cancelable: refusing it takes the decision and nothing moves. */
@@ -12183,15 +12195,27 @@ Written by the listbox. */
 
 `<option selected>` reflects to `defaultSelected` and `option.selected` is
 live state that does not reflect, and those are two different facts. This
-element has one `selected` doing both jobs, so what is captured here is what
-the markup said at upgrade, before anything could overwrite it: read the
-attribute later and the listbox's own writes answer instead.
-
-**The deeper half is 302 and is not this.** State reflecting under the
-declaration's name is the fault `TreeItem` already avoids by mirroring to
-`data-selected`, and four families here still write `selected` back into a
-consumer's markup. Splitting them means moving what every stylesheet selects
-on, which is a change of its own rather than a property being added. */
+element has one `selected` doing both jobs, so the declaration is the
+attribute and the state is the property.
+
+**The attribute, read when it is asked for, and never a snapshot taken in
+the constructor.** A field initializer runs there, and an element the HTML
+parser created has none of its attributes yet at that moment: measured on
+this element, on `Radio` and on `Toggle`, `<helix-option value="a"
+selected>` reported `defaultSelected` as `false` both from parsed markup
+and from `createElement` followed by `setAttribute`, which is every way a
+consumer writes one. The snapshot could only ever be true for an element
+already in the document when `customElements.define` ran.
+
+Nothing overwrites it either, which is what makes reading it late correct
+rather than merely later: `selected` does not reflect, for the reason
+`willUpdate` records, so the listbox's writes never reach the attribute and
+what it says is what the markup said.
+
+**The deeper half is not this.** State reflecting under the declaration's
+name is the fault `TreeItem` avoids by mirroring to `data-selected`.
+Splitting them means moving what every stylesheet selects on, which is a
+change of its own rather than a property being added. */
   "prop:defaultSelected"?: (HelixOption["defaultSelected"]) | undefined;
   /** Fired when this choice is made. Cancelable: refusing it takes the decision and nothing moves. */
   "on:helix-select"?: ((e: HelixOptionHelixSelectElementEvent) => void) | undefined;
@@ -13590,9 +13614,22 @@ Written by the group. */
 
 `<option selected>` reflects to `defaultSelected` and `option.selected` is
 live state that does not reflect, and those are two different facts. This
-element has one `selected` doing both jobs, so what is captured here is what
-the markup said at upgrade, before anything could overwrite it: read the
-attribute later and the listbox's own writes answer instead.
+element has one `selected` doing both jobs, so the declaration is the
+attribute and the state is the property.
+
+**The attribute, read when it is asked for, and never a snapshot taken in
+the constructor.** A field initializer runs there, and an element the HTML
+parser created has none of its attributes yet at that moment: measured on
+this element, on `Option` and on `Toggle`, `<helix-radio value="a"
+selected>` reported `defaultSelected` as `false` both from parsed markup
+and from `createElement` followed by `setAttribute`, which is every way a
+consumer writes one. The snapshot could only ever be true for an element
+already in the document when `customElements.define` ran.
+
+Nothing overwrites it either, which is what makes reading it late correct
+rather than merely later: `selected` does not reflect, for the reason
+`willUpdate` records, so the group's writes never reach the attribute and
+what it says is what the markup said.
 
 **The deeper half is not this.** State reflecting under the declaration's
 name is the fault `TreeItem` avoids by mirroring to `data-selected`.
@@ -13667,9 +13704,22 @@ Written by the group. */
 
 `<option selected>` reflects to `defaultSelected` and `option.selected` is
 live state that does not reflect, and those are two different facts. This
-element has one `selected` doing both jobs, so what is captured here is what
-the markup said at upgrade, before anything could overwrite it: read the
-attribute later and the listbox's own writes answer instead.
+element has one `selected` doing both jobs, so the declaration is the
+attribute and the state is the property.
+
+**The attribute, read when it is asked for, and never a snapshot taken in
+the constructor.** A field initializer runs there, and an element the HTML
+parser created has none of its attributes yet at that moment: measured on
+this element, on `Option` and on `Toggle`, `<helix-radio value="a"
+selected>` reported `defaultSelected` as `false` both from parsed markup
+and from `createElement` followed by `setAttribute`, which is every way a
+consumer writes one. The snapshot could only ever be true for an element
+already in the document when `customElements.define` ran.
+
+Nothing overwrites it either, which is what makes reading it late correct
+rather than merely later: `selected` does not reflect, for the reason
+`willUpdate` records, so the group's writes never reach the attribute and
+what it says is what the markup said.
 
 **The deeper half is not this.** State reflecting under the declaration's
 name is the fault `TreeItem` avoids by mirroring to `data-selected`.
@@ -18309,9 +18359,22 @@ export type HelixToggleProps = {
 
 `<option selected>` reflects to `defaultSelected` and `option.selected` is
 live state that does not reflect, and those are two different facts. This
-element has one `selected` doing both jobs, so what is captured here is what
-the markup said at upgrade, before anything could overwrite it: read the
-attribute later and the listbox's own writes answer instead.
+element has one `selected` doing both jobs, so the declaration is the
+attribute and the state is the property.
+
+**The attribute, read when it is asked for, and never a snapshot taken in
+the constructor.** A field initializer runs there, and an element the HTML
+parser created has none of its attributes yet at that moment: measured on
+this element, on `Option` and on `Radio`, `<helix-toggle value="light"
+selected>` reported `defaultSelected` as `false` both from parsed markup
+and from `createElement` followed by `setAttribute`, which is every way a
+consumer writes one. The snapshot could only ever be true for an element
+already in the document when `customElements.define` ran.
+
+Nothing overwrites it either, which is what makes reading it late correct
+rather than merely later: `selected` does not reflect, for the reason
+`willUpdate` records, so the group's writes never reach the attribute and
+what it says is what the markup said.
 
 **The deeper half is not this.** State reflecting under the declaration's
 name is the fault `TreeItem` avoids by mirroring to `data-selected`.
@@ -18342,9 +18405,22 @@ export type HelixToggleSolidJsProps = {
 
 `<option selected>` reflects to `defaultSelected` and `option.selected` is
 live state that does not reflect, and those are two different facts. This
-element has one `selected` doing both jobs, so what is captured here is what
-the markup said at upgrade, before anything could overwrite it: read the
-attribute later and the listbox's own writes answer instead.
+element has one `selected` doing both jobs, so the declaration is the
+attribute and the state is the property.
+
+**The attribute, read when it is asked for, and never a snapshot taken in
+the constructor.** A field initializer runs there, and an element the HTML
+parser created has none of its attributes yet at that moment: measured on
+this element, on `Option` and on `Radio`, `<helix-toggle value="light"
+selected>` reported `defaultSelected` as `false` both from parsed markup
+and from `createElement` followed by `setAttribute`, which is every way a
+consumer writes one. The snapshot could only ever be true for an element
+already in the document when `customElements.define` ran.
+
+Nothing overwrites it either, which is what makes reading it late correct
+rather than merely later: `selected` does not reflect, for the reason
+`willUpdate` records, so the group's writes never reach the attribute and
+what it says is what the markup said.
 
 **The deeper half is not this.** State reflecting under the declaration's
 name is the fault `TreeItem` avoids by mirroring to `data-selected`.
@@ -25278,9 +25354,12 @@ export type CustomElements = {
    * difference is the space between days, which belongs to the track rather than
    * to a `gap`, so a range can paint across the whole track and stay continuous.
    *
-   * Days from the neighboring months stay in place and stay selectable, marked
-   * quieter rather than hidden, so the first and last weeks are whole and the
-   * grid reads as a continuous run of dates.
+   * Days from the neighboring months stay in place, marked quieter rather than
+   * hidden, so the first and last weeks are whole rows rather than ragged ones.
+   * They are filler and take no click, which the pointer says: no hover, and the
+   * cursor a box that does nothing has. At `months="2"` the same date is a
+   * trailing cell in one grid and a real one in the next, so a filler day that
+   * could be chosen would put one answer on the page twice.
    *
    * ## Attributes & Properties
    *
@@ -31209,15 +31288,27 @@ export type CustomElements = {
    *
    * `<option selected>` reflects to `defaultSelected` and `option.selected` is
    * live state that does not reflect, and those are two different facts. This
-   * element has one `selected` doing both jobs, so what is captured here is what
-   * the markup said at upgrade, before anything could overwrite it: read the
-   * attribute later and the listbox's own writes answer instead.
-   *
-   * **The deeper half is 302 and is not this.** State reflecting under the
-   * declaration's name is the fault `TreeItem` already avoids by mirroring to
-   * `data-selected`, and four families here still write `selected` back into a
-   * consumer's markup. Splitting them means moving what every stylesheet selects
-   * on, which is a change of its own rather than a property being added. (property only)
+   * element has one `selected` doing both jobs, so the declaration is the
+   * attribute and the state is the property.
+   *
+   * **The attribute, read when it is asked for, and never a snapshot taken in
+   * the constructor.** A field initializer runs there, and an element the HTML
+   * parser created has none of its attributes yet at that moment: measured on
+   * this element, on `Radio` and on `Toggle`, `<helix-option value="a"
+   * selected>` reported `defaultSelected` as `false` both from parsed markup
+   * and from `createElement` followed by `setAttribute`, which is every way a
+   * consumer writes one. The snapshot could only ever be true for an element
+   * already in the document when `customElements.define` ran.
+   *
+   * Nothing overwrites it either, which is what makes reading it late correct
+   * rather than merely later: `selected` does not reflect, for the reason
+   * `willUpdate` records, so the listbox's writes never reach the attribute and
+   * what it says is what the markup said.
+   *
+   * **The deeper half is not this.** State reflecting under the declaration's
+   * name is the fault `TreeItem` avoids by mirroring to `data-selected`.
+   * Splitting them means moving what every stylesheet selects on, which is a
+   * change of its own rather than a property being added. (property only)
    * - `text`: The words, for a listbox that has to match text against them.
    *
    * Read from the rendered content rather than required as a property, because
@@ -32715,9 +32806,22 @@ export type CustomElements = {
    *
    * `<option selected>` reflects to `defaultSelected` and `option.selected` is
    * live state that does not reflect, and those are two different facts. This
-   * element has one `selected` doing both jobs, so what is captured here is what
-   * the markup said at upgrade, before anything could overwrite it: read the
-   * attribute later and the listbox's own writes answer instead.
+   * element has one `selected` doing both jobs, so the declaration is the
+   * attribute and the state is the property.
+   *
+   * **The attribute, read when it is asked for, and never a snapshot taken in
+   * the constructor.** A field initializer runs there, and an element the HTML
+   * parser created has none of its attributes yet at that moment: measured on
+   * this element, on `Option` and on `Toggle`, `<helix-radio value="a"
+   * selected>` reported `defaultSelected` as `false` both from parsed markup
+   * and from `createElement` followed by `setAttribute`, which is every way a
+   * consumer writes one. The snapshot could only ever be true for an element
+   * already in the document when `customElements.define` ran.
+   *
+   * Nothing overwrites it either, which is what makes reading it late correct
+   * rather than merely later: `selected` does not reflect, for the reason
+   * `willUpdate` records, so the group's writes never reach the attribute and
+   * what it says is what the markup said.
    *
    * **The deeper half is not this.** State reflecting under the declaration's
    * name is the fault `TreeItem` avoids by mirroring to `data-selected`.
@@ -34399,9 +34503,9 @@ export type CustomElements = {
    * - `--slider-track-image`: The whole track, for a slider whose color is the value. (default: `undefined`)
    * - `--slider-track-size`: How thick the track is. The progress bar's own size by default, the two being the same object. (default: `undefined`)
    * - `--slider-fraction`: The value as a fraction of the range, 0 to 1. (default: `undefined`)
-   * - `--slider-from`: Where the filled span starts, as a percentage of the track. (default: `undefined`)
+   * - `--slider-from`: Where a range's filled span starts, as a fraction of the track, 0 to 1. (default: `undefined`)
    * - `--slider-marker-at`: Where one marker sits, as a percentage of the track. (default: `undefined`)
-   * - `--slider-to`: Where the filled span ends, as a percentage of the track. (default: `undefined`)
+   * - `--slider-to`: Where a range's filled span ends, as a fraction of the track, 0 to 1. (default: `undefined`)
    *
    * ## CSS Parts
    *
@@ -37589,6 +37693,8 @@ export type CustomElements = {
    * Areas where markup can be added to the component.
    *
    * - `(default)`: The group's items.
+   * - `end`: Whatever sits after the track on its own line, such as a count or a reset.
+   * - `start`: Whatever sits before the track on its own line, such as an icon or a caption.
    *
    * ## Methods
    *
@@ -37690,9 +37796,22 @@ export type CustomElements = {
    *
    * `<option selected>` reflects to `defaultSelected` and `option.selected` is
    * live state that does not reflect, and those are two different facts. This
-   * element has one `selected` doing both jobs, so what is captured here is what
-   * the markup said at upgrade, before anything could overwrite it: read the
-   * attribute later and the listbox's own writes answer instead.
+   * element has one `selected` doing both jobs, so the declaration is the
+   * attribute and the state is the property.
+   *
+   * **The attribute, read when it is asked for, and never a snapshot taken in
+   * the constructor.** A field initializer runs there, and an element the HTML
+   * parser created has none of its attributes yet at that moment: measured on
+   * this element, on `Option` and on `Radio`, `<helix-toggle value="light"
+   * selected>` reported `defaultSelected` as `false` both from parsed markup
+   * and from `createElement` followed by `setAttribute`, which is every way a
+   * consumer writes one. The snapshot could only ever be true for an element
+   * already in the document when `customElements.define` ran.
+   *
+   * Nothing overwrites it either, which is what makes reading it late correct
+   * rather than merely later: `selected` does not reflect, for the reason
+   * `willUpdate` records, so the group's writes never reach the attribute and
+   * what it says is what the markup said.
    *
    * **The deeper half is not this.** State reflecting under the declaration's
    * name is the fault `TreeItem` avoids by mirroring to `data-selected`.
@@ -37753,7 +37872,7 @@ export type CustomElements = {
    *
    * Custom selectors for styling elements within the component.
    *
-   * - `item`: The button or anchor.
+   * - `item`: The radio button.
    *
    * ## CSS States
    *
@@ -44544,9 +44663,12 @@ export type CustomElementsSolidJs = {
    * difference is the space between days, which belongs to the track rather than
    * to a `gap`, so a range can paint across the whole track and stay continuous.
    *
-   * Days from the neighboring months stay in place and stay selectable, marked
-   * quieter rather than hidden, so the first and last weeks are whole and the
-   * grid reads as a continuous run of dates.
+   * Days from the neighboring months stay in place, marked quieter rather than
+   * hidden, so the first and last weeks are whole rows rather than ragged ones.
+   * They are filler and take no click, which the pointer says: no hover, and the
+   * cursor a box that does nothing has. At `months="2"` the same date is a
+   * trailing cell in one grid and a real one in the next, so a filler day that
+   * could be chosen would put one answer on the page twice.
    *
    * ## Attributes & Properties
    *
@@ -50601,15 +50723,27 @@ export type CustomElementsSolidJs = {
    *
    * `<option selected>` reflects to `defaultSelected` and `option.selected` is
    * live state that does not reflect, and those are two different facts. This
-   * element has one `selected` doing both jobs, so what is captured here is what
-   * the markup said at upgrade, before anything could overwrite it: read the
-   * attribute later and the listbox's own writes answer instead.
-   *
-   * **The deeper half is 302 and is not this.** State reflecting under the
-   * declaration's name is the fault `TreeItem` already avoids by mirroring to
-   * `data-selected`, and four families here still write `selected` back into a
-   * consumer's markup. Splitting them means moving what every stylesheet selects
-   * on, which is a change of its own rather than a property being added. (property only)
+   * element has one `selected` doing both jobs, so the declaration is the
+   * attribute and the state is the property.
+   *
+   * **The attribute, read when it is asked for, and never a snapshot taken in
+   * the constructor.** A field initializer runs there, and an element the HTML
+   * parser created has none of its attributes yet at that moment: measured on
+   * this element, on `Radio` and on `Toggle`, `<helix-option value="a"
+   * selected>` reported `defaultSelected` as `false` both from parsed markup
+   * and from `createElement` followed by `setAttribute`, which is every way a
+   * consumer writes one. The snapshot could only ever be true for an element
+   * already in the document when `customElements.define` ran.
+   *
+   * Nothing overwrites it either, which is what makes reading it late correct
+   * rather than merely later: `selected` does not reflect, for the reason
+   * `willUpdate` records, so the listbox's writes never reach the attribute and
+   * what it says is what the markup said.
+   *
+   * **The deeper half is not this.** State reflecting under the declaration's
+   * name is the fault `TreeItem` avoids by mirroring to `data-selected`.
+   * Splitting them means moving what every stylesheet selects on, which is a
+   * change of its own rather than a property being added. (property only)
    * - `text`: The words, for a listbox that has to match text against them.
    *
    * Read from the rendered content rather than required as a property, because
@@ -52144,9 +52278,22 @@ export type CustomElementsSolidJs = {
    *
    * `<option selected>` reflects to `defaultSelected` and `option.selected` is
    * live state that does not reflect, and those are two different facts. This
-   * element has one `selected` doing both jobs, so what is captured here is what
-   * the markup said at upgrade, before anything could overwrite it: read the
-   * attribute later and the listbox's own writes answer instead.
+   * element has one `selected` doing both jobs, so the declaration is the
+   * attribute and the state is the property.
+   *
+   * **The attribute, read when it is asked for, and never a snapshot taken in
+   * the constructor.** A field initializer runs there, and an element the HTML
+   * parser created has none of its attributes yet at that moment: measured on
+   * this element, on `Option` and on `Toggle`, `<helix-radio value="a"
+   * selected>` reported `defaultSelected` as `false` both from parsed markup
+   * and from `createElement` followed by `setAttribute`, which is every way a
+   * consumer writes one. The snapshot could only ever be true for an element
+   * already in the document when `customElements.define` ran.
+   *
+   * Nothing overwrites it either, which is what makes reading it late correct
+   * rather than merely later: `selected` does not reflect, for the reason
+   * `willUpdate` records, so the group's writes never reach the attribute and
+   * what it says is what the markup said.
    *
    * **The deeper half is not this.** State reflecting under the declaration's
    * name is the fault `TreeItem` avoids by mirroring to `data-selected`.
@@ -53869,9 +54016,9 @@ export type CustomElementsSolidJs = {
    * - `--slider-track-image`: The whole track, for a slider whose color is the value. (default: `undefined`)
    * - `--slider-track-size`: How thick the track is. The progress bar's own size by default, the two being the same object. (default: `undefined`)
    * - `--slider-fraction`: The value as a fraction of the range, 0 to 1. (default: `undefined`)
-   * - `--slider-from`: Where the filled span starts, as a percentage of the track. (default: `undefined`)
+   * - `--slider-from`: Where a range's filled span starts, as a fraction of the track, 0 to 1. (default: `undefined`)
    * - `--slider-marker-at`: Where one marker sits, as a percentage of the track. (default: `undefined`)
-   * - `--slider-to`: Where the filled span ends, as a percentage of the track. (default: `undefined`)
+   * - `--slider-to`: Where a range's filled span ends, as a fraction of the track, 0 to 1. (default: `undefined`)
    *
    * ## CSS Parts
    *
@@ -57137,6 +57284,8 @@ export type CustomElementsSolidJs = {
    * Areas where markup can be added to the component.
    *
    * - `(default)`: The group's items.
+   * - `end`: Whatever sits after the track on its own line, such as a count or a reset.
+   * - `start`: Whatever sits before the track on its own line, such as an icon or a caption.
    *
    * ## Methods
    *
@@ -57241,9 +57390,22 @@ export type CustomElementsSolidJs = {
    *
    * `<option selected>` reflects to `defaultSelected` and `option.selected` is
    * live state that does not reflect, and those are two different facts. This
-   * element has one `selected` doing both jobs, so what is captured here is what
-   * the markup said at upgrade, before anything could overwrite it: read the
-   * attribute later and the listbox's own writes answer instead.
+   * element has one `selected` doing both jobs, so the declaration is the
+   * attribute and the state is the property.
+   *
+   * **The attribute, read when it is asked for, and never a snapshot taken in
+   * the constructor.** A field initializer runs there, and an element the HTML
+   * parser created has none of its attributes yet at that moment: measured on
+   * this element, on `Option` and on `Radio`, `<helix-toggle value="light"
+   * selected>` reported `defaultSelected` as `false` both from parsed markup
+   * and from `createElement` followed by `setAttribute`, which is every way a
+   * consumer writes one. The snapshot could only ever be true for an element
+   * already in the document when `customElements.define` ran.
+   *
+   * Nothing overwrites it either, which is what makes reading it late correct
+   * rather than merely later: `selected` does not reflect, for the reason
+   * `willUpdate` records, so the group's writes never reach the attribute and
+   * what it says is what the markup said.
    *
    * **The deeper half is not this.** State reflecting under the declaration's
    * name is the fault `TreeItem` avoids by mirroring to `data-selected`.
@@ -57304,7 +57466,7 @@ export type CustomElementsSolidJs = {
    *
    * Custom selectors for styling elements within the component.
    *
-   * - `item`: The button or anchor.
+   * - `item`: The radio button.
    *
    * ## CSS States
    *
@@ -59731,11 +59893,11 @@ export type CustomCssProperties = {
   "--slider-track-size"?: (string) | undefined;
   /** The value as a fraction of the range, 0 to 1. */
   "--slider-fraction"?: (string) | undefined;
-  /** Where the filled span starts, as a percentage of the track. */
+  /** Where a range's filled span starts, as a fraction of the track, 0 to 1. */
   "--slider-from"?: (string) | undefined;
   /** Where one marker sits, as a percentage of the track. */
   "--slider-marker-at"?: (string) | undefined;
-  /** Where the filled span ends, as a percentage of the track. */
+  /** Where a range's filled span ends, as a fraction of the track, 0 to 1. */
   "--slider-to"?: (string) | undefined;
   /** How much of the line's color the wash takes where it meets the line. */
   "--sparkline-area-opacity"?: (string) | undefined;

package/types/vue.d.ts

@@ -6233,15 +6233,27 @@ Written by the listbox. */
 
 `<option selected>` reflects to `defaultSelected` and `option.selected` is
 live state that does not reflect, and those are two different facts. This
-element has one `selected` doing both jobs, so what is captured here is what
-the markup said at upgrade, before anything could overwrite it: read the
-attribute later and the listbox's own writes answer instead.
-
-**The deeper half is 302 and is not this.** State reflecting under the
-declaration's name is the fault `TreeItem` already avoids by mirroring to
-`data-selected`, and four families here still write `selected` back into a
-consumer's markup. Splitting them means moving what every stylesheet selects
-on, which is a change of its own rather than a property being added. */
+element has one `selected` doing both jobs, so the declaration is the
+attribute and the state is the property.
+
+**The attribute, read when it is asked for, and never a snapshot taken in
+the constructor.** A field initializer runs there, and an element the HTML
+parser created has none of its attributes yet at that moment: measured on
+this element, on `Radio` and on `Toggle`, `<helix-option value="a"
+selected>` reported `defaultSelected` as `false` both from parsed markup
+and from `createElement` followed by `setAttribute`, which is every way a
+consumer writes one. The snapshot could only ever be true for an element
+already in the document when `customElements.define` ran.
+
+Nothing overwrites it either, which is what makes reading it late correct
+rather than merely later: `selected` does not reflect, for the reason
+`willUpdate` records, so the listbox's writes never reach the attribute and
+what it says is what the markup said.
+
+**The deeper half is not this.** State reflecting under the declaration's
+name is the fault `TreeItem` avoids by mirroring to `data-selected`.
+Splitting them means moving what every stylesheet selects on, which is a
+change of its own rather than a property being added. */
   defaultSelected?: (HelixOption["defaultSelected"]) | undefined;
 };
 
@@ -6995,9 +7007,22 @@ Written by the group. */
 
 `<option selected>` reflects to `defaultSelected` and `option.selected` is
 live state that does not reflect, and those are two different facts. This
-element has one `selected` doing both jobs, so what is captured here is what
-the markup said at upgrade, before anything could overwrite it: read the
-attribute later and the listbox's own writes answer instead.
+element has one `selected` doing both jobs, so the declaration is the
+attribute and the state is the property.
+
+**The attribute, read when it is asked for, and never a snapshot taken in
+the constructor.** A field initializer runs there, and an element the HTML
+parser created has none of its attributes yet at that moment: measured on
+this element, on `Option` and on `Toggle`, `<helix-radio value="a"
+selected>` reported `defaultSelected` as `false` both from parsed markup
+and from `createElement` followed by `setAttribute`, which is every way a
+consumer writes one. The snapshot could only ever be true for an element
+already in the document when `customElements.define` ran.
+
+Nothing overwrites it either, which is what makes reading it late correct
+rather than merely later: `selected` does not reflect, for the reason
+`willUpdate` records, so the group's writes never reach the attribute and
+what it says is what the markup said.
 
 **The deeper half is not this.** State reflecting under the declaration's
 name is the fault `TreeItem` avoids by mirroring to `data-selected`.
@@ -9390,9 +9415,22 @@ export type HelixToggleVueProps = {
 
 `<option selected>` reflects to `defaultSelected` and `option.selected` is
 live state that does not reflect, and those are two different facts. This
-element has one `selected` doing both jobs, so what is captured here is what
-the markup said at upgrade, before anything could overwrite it: read the
-attribute later and the listbox's own writes answer instead.
+element has one `selected` doing both jobs, so the declaration is the
+attribute and the state is the property.
+
+**The attribute, read when it is asked for, and never a snapshot taken in
+the constructor.** A field initializer runs there, and an element the HTML
+parser created has none of its attributes yet at that moment: measured on
+this element, on `Option` and on `Radio`, `<helix-toggle value="light"
+selected>` reported `defaultSelected` as `false` both from parsed markup
+and from `createElement` followed by `setAttribute`, which is every way a
+consumer writes one. The snapshot could only ever be true for an element
+already in the document when `customElements.define` ran.
+
+Nothing overwrites it either, which is what makes reading it late correct
+rather than merely later: `selected` does not reflect, for the reason
+`willUpdate` records, so the group's writes never reach the attribute and
+what it says is what the markup said.
 
 **The deeper half is not this.** State reflecting under the declaration's
 name is the fault `TreeItem` avoids by mirroring to `data-selected`.
@@ -11157,11 +11195,11 @@ export type CustomCssProperties = {
   "--slider-track-size"?: (string) | undefined;
   /** The value as a fraction of the range, 0 to 1. */
   "--slider-fraction"?: (string) | undefined;
-  /** Where the filled span starts, as a percentage of the track. */
+  /** Where a range's filled span starts, as a fraction of the track, 0 to 1. */
   "--slider-from"?: (string) | undefined;
   /** Where one marker sits, as a percentage of the track. */
   "--slider-marker-at"?: (string) | undefined;
-  /** Where the filled span ends, as a percentage of the track. */
+  /** Where a range's filled span ends, as a fraction of the track, 0 to 1. */
   "--slider-to"?: (string) | undefined;
   /** How much of the line's color the wash takes where it meets the line. */
   "--sparkline-area-opacity"?: (string) | undefined;
@@ -11561,7 +11599,7 @@ export interface WcToolkitVueGlobalComponents {
     HelixDateInputVueProps,
     HelixDateInputVueEvents
   >;
-  /** Six week rows always, so the grid keeps one height and a month change does not move whatever sits beneath it.  The column track is wider than the day, and the day is centered in it. The difference is the space between days, which belongs to the track rather than to a 'gap', so a range can paint across the whole track and stay continuous.  Days from the neighboring months stay in place and stay selectable, marked quieter rather than hidden, so the first and last weeks are whole and the grid reads as a continuous run of dates. */
+  /** Six week rows always, so the grid keeps one height and a month change does not move whatever sits beneath it.  The column track is wider than the day, and the day is centered in it. The difference is the space between days, which belongs to the track rather than to a 'gap', so a range can paint across the whole track and stay continuous.  Days from the neighboring months stay in place, marked quieter rather than hidden, so the first and last weeks are whole rows rather than ragged ones. They are filler and take no click, which the pointer says: no hover, and the cursor a box that does nothing has. At 'months="2"' the same date is a trailing cell in one grid and a real one in the next, so a filler day that could be chosen would put one answer on the page twice. */
   "helix-date-picker": DefineCustomElement<
     HelixDatePicker,
     HelixDatePickerVueProps,