@fusion.dev/helix 0.42.0 → 0.44.0

package/custom-elements.json

@@ -15216,7 +15216,7 @@
           "helix": {
             "category": "forms",
             "since": "0.1.0",
-            "status": "experimental",
+            "status": "stable",
             "documentation": "https://fusion.dev/helix/components/chat",
             "tier": "styled",
             "group": "Chat",
@@ -16246,7 +16246,7 @@
           "helix": {
             "category": "feedback",
             "since": "0.1.0",
-            "status": "experimental",
+            "status": "stable",
             "documentation": "https://fusion.dev/helix/components/chat",
             "tier": "styled",
             "group": "Chat",
@@ -17943,7 +17943,7 @@
           "helix": {
             "category": "feedback",
             "since": "0.1.0",
-            "status": "experimental",
+            "status": "stable",
             "documentation": "https://fusion.dev/helix/components/chat",
             "tier": "styled",
             "group": "Chat",
@@ -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",
@@ -72243,6 +72243,20 @@
                 "module": "src/notifications/group/notification-group.ts"
               }
             },
+            {
+              "kind": "field",
+              "name": "counted",
+              "type": {
+                "text": "number | undefined"
+              },
+              "privacy": "private",
+              "description": "The same number where anything can know it, and nothing where nothing can.\n\n**A server has no rows to count and must not say zero.** `items` reads\n`knownChildren`, which is empty on a server and while hydrating what one\nsent, so a group written around three notifications with no `count` of its\nown served `<span part=\"count\">0</span>`: a crawler, and a reader before the\npage has run, given a group that says it holds nothing over the three rows\nunderneath it. Not knowing is not zero, which is the rule `MixinCollection`\nalready states about an empty list.\n\nA declared `count` is a fact about the group rather than about its children,\nso it serves whole, which is the shape a feed trimmed by a server already\nwants: it is the number the rows were cut from.",
+              "readonly": true,
+              "inheritedFrom": {
+                "name": "HelixHeadlessNotificationGroup",
+                "module": "src/notifications/group/notification-group.ts"
+              }
+            },
             {
               "kind": "method",
               "name": "assign",
@@ -72268,20 +72282,6 @@
                 "module": "src/notifications/group/notification-group.ts"
               }
             },
-            {
-              "kind": "field",
-              "name": "folded",
-              "type": {
-                "text": "number"
-              },
-              "privacy": "private",
-              "description": "How many rows the collapse is hiding, for the control to say so.",
-              "readonly": true,
-              "inheritedFrom": {
-                "name": "HelixHeadlessNotificationGroup",
-                "module": "src/notifications/group/notification-group.ts"
-              }
-            },
             {
               "kind": "field",
               "name": "tier",
@@ -72641,7 +72641,7 @@
           "helix": {
             "category": "feedback",
             "since": "0.24.0",
-            "status": "experimental",
+            "status": "stable",
             "documentation": "https://fusion.dev/helix/components/notifications",
             "aliases": [
               "NotificationSection",
@@ -73078,6 +73078,14 @@
                 "name": "HelixHeadlessNotification",
                 "module": "src/notifications/notification/notification.ts"
               }
+            },
+            {
+              "description": "Replaces the glyph inside the dismiss control, which is drawn only where the row is `dismissible`.",
+              "name": "dismiss",
+              "inheritedFrom": {
+                "name": "HelixHeadlessNotification",
+                "module": "src/notifications/notification/notification.ts"
+              }
             }
           ],
           "members": [
@@ -73710,7 +73718,7 @@
           "helix": {
             "category": "feedback",
             "since": "0.1.0",
-            "status": "experimental",
+            "status": "stable",
             "documentation": "https://fusion.dev/helix/components/notifications",
             "tier": "styled",
             "group": "Notifications",
@@ -74275,7 +74283,7 @@
                   "text": "void"
                 }
               },
-              "description": "Says whether anything in the feed has media, so every item can hold the\ncolumn open whether or not it has one of its own.\n\n**A fact no item can answer for itself**, which is why it is here. An item\nknows about its own media slot and nothing about its neighbors, so a feed\nwhere some rows have an avatar and some do not draws two different left\nedges for its text: measured on a four item feed, the rows without media\nstarted their text 32 pixels to the left of the rows with it. The styled\ntier turns this into a width; this tier ships no stylesheet and is\nunaffected.\n\nRead off the light DOM rather than off the items, so it does not depend on\nwhich children have upgraded by the time this runs.",
+              "description": "Says whether anything in the feed has media, so every item can hold the\ncolumn open whether or not it has one of its own.\n\n**A fact no item can answer for itself**, which is why it is here. An item\nknows about its own media slot and nothing about its neighbors, so a feed\nwhere some rows have an avatar and some do not draws two different left\nedges for its text: measured on a four item feed, the rows without media\nstarted their text 32 pixels to the left of the rows with it. The styled\ntier turns this into a width; this tier ships no stylesheet and is\nunaffected.\n\n**What is asked of each row is its light DOM, not the row.** A notification\npublishes no property for this, and asking one would make the answer depend\non the row having drawn itself; a `[slot=\"media\"]` child is there from the\nmoment the markup is parsed. The rows themselves come from `items`, which\ndoes need them upgraded, and that is the honest limit rather than a claim\nthis had made the other way: a row that upgrades late is counted on the next\nupdate, which its own `slotchange` asks for.",
               "inheritedFrom": {
                 "name": "HelixHeadlessNotifications",
                 "module": "src/notifications/root/notifications-root.ts"
@@ -74661,7 +74669,7 @@
           "helix": {
             "category": "feedback",
             "since": "0.1.0",
-            "status": "experimental",
+            "status": "stable",
             "documentation": "https://fusion.dev/helix/components/notifications",
             "tier": "styled",
             "group": "Notifications",
@@ -78526,17 +78534,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 +90015,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 +101155,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 +101171,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 +102344,7 @@
           "helix": {
             "category": "forms",
             "since": "0.1.0",
-            "status": "experimental",
+            "status": "stable",
             "documentation": "https://fusion.dev/helix/components/slider",
             "aliases": [
               "Range",
@@ -104062,7 +104050,7 @@
           "helix": {
             "category": "actions",
             "since": "0.1.0",
-            "status": "experimental",
+            "status": "stable",
             "documentation": "https://fusion.dev/helix/components/speed-dial",
             "aliases": [
               "Speed dial action",
@@ -104835,7 +104823,7 @@
           "helix": {
             "category": "actions",
             "since": "0.1.0",
-            "status": "experimental",
+            "status": "stable",
             "documentation": "https://fusion.dev/helix/components/speed-dial",
             "aliases": [
               "FAB",
@@ -105728,7 +105716,7 @@
                   }
                 }
               ],
-              "description": "Asks to move, and applies it where the position is this element's to move.\n\nNot announced per step: `helix-before-resize` is the settling, below. A drag that\nannounced every position would be asking a consumer to record a hundred\ndecisions to keep one.",
+              "description": "Moves the divider under a gesture that is still happening.\n\nNot announced per step: `helix-before-resize` is the settling, below. A drag that\nannounced every position would be asking a consumer to record a hundred\ndecisions to keep one.\n\n**A drag only, which is the whole of why applying before announcing is\nright here.** The divider has to follow the hand, and the one number worth\na decision is where the hand let go. Nothing discrete calls this: a key and\na double click go straight to `settle`, so their announcement comes before\ntheir change and refusing one takes the decision, and the corner's arrows\nalready did.",
               "inheritedFrom": {
                 "name": "HelixHeadlessSplitter",
                 "module": "src/splitter/root/splitter-root.ts"
@@ -105751,7 +105739,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.",
+              "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.",
               "inheritedFrom": {
                 "name": "HelixHeadlessSplitter",
                 "module": "src/splitter/root/splitter-root.ts"
@@ -106554,7 +106542,7 @@
               "type": {
                 "text": "HelixBeforeCollapseEvent"
               },
-              "description": "Fired before a pane shuts or reopens, and cancelable.",
+              "description": "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.",
               "name": "helix-before-collapse",
               "reactProp": "onhelix-before-collapse",
               "inheritedFrom": {
@@ -106566,7 +106554,7 @@
               "type": {
                 "text": "HelixBeforeResizeEvent"
               },
-              "description": "Fired before the divider settles, and cancelable.",
+              "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.",
               "name": "helix-before-resize",
               "reactProp": "onhelix-before-resize",
               "inheritedFrom": {
@@ -124112,7 +124100,7 @@
           "summary": "One message in the toast region.",
           "helix": {
             "since": "0.1.0",
-            "status": "experimental",
+            "status": "stable",
             "documentation": "https://fusion.dev/helix/components/toast",
             "tier": "styled",
             "group": "Toast",
@@ -124735,12 +124723,11 @@
           "helix": {
             "category": "overlays",
             "since": "0.1.0",
-            "status": "experimental",
+            "status": "stable",
             "documentation": "https://fusion.dev/helix/components/toast",
             "aliases": [
               "Toaster",
-              "Snackbar",
-              "Notifications"
+              "Snackbar"
             ],
             "tier": "styled",
             "group": "Toast",
@@ -124969,6 +124956,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 +125347,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 +126075,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 +126233,7 @@
           "name": "HelixToggle",
           "cssParts": [
             {
-              "description": "The button or anchor.",
+              "description": "The radio button.",
               "name": "item",
               "inheritedFrom": {
                 "name": "HelixHeadlessToggle",
@@ -126255,17 +126273,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 +126687,7 @@
           "helix": {
             "category": "actions",
             "since": "0.1.0",
-            "status": "experimental",
+            "status": "stable",
             "documentation": "https://fusion.dev/helix/components/toggle",
             "aliases": [
               "Segment",
@@ -129852,18 +129860,6 @@
                 "name": "HelixHeadlessTour",
                 "module": "src/tour/root/tour-root.ts"
               }
-            },
-            {
-              "type": {
-                "text": "Event"
-              },
-              "description": "Says the state moved, carrying `newState` and `oldState`.",
-              "name": "toggle",
-              "reactProp": "ontoggle",
-              "inheritedFrom": {
-                "name": "HelixHeadlessTour",
-                "module": "src/tour/root/tour-root.ts"
-              }
             }
           ],
           "cssStates": [

package/dist/chat/composer/chat-composer.d.ts

@@ -11,7 +11,7 @@ import type { CSSResultGroup } from 'lit';
  * a ceiling eats the transcript it belongs to.
  *
  * @since 0.1.0
- * @status experimental
+ * @status stable
  * @category forms
  * @documentation https://fusion.dev/helix/components/chat
  *

package/dist/chat/message/chat-message.d.ts

@@ -13,7 +13,7 @@ import type { CSSResultGroup } from 'lit';
  * is the signal, and decorating it competes with the thing it is decorating.
  *
  * @since 0.1.0
- * @status experimental
+ * @status stable
  * @category feedback
  * @documentation https://fusion.dev/helix/components/chat
  *

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

@@ -19,7 +19,7 @@ import '../message/chat-message.js';
  * offering it.
  *
  * @since 0.1.0
- * @status experimental
+ * @status stable
  * @category feedback
  * @documentation https://fusion.dev/helix/components/chat
  *

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/element-events.generated.js

@@ -138,13 +138,7 @@ registerElementEvents({
     'helix-toggle': ['helix-select'],
     'helix-toggle-group': ['change', 'helix-before-change', 'helix-select', 'input'],
     'helix-tooltip': ['helix-before-close', 'helix-before-open', 'toggle'],
-    'helix-tour': [
-        'helix-before-activate',
-        'helix-before-close',
-        'helix-complete',
-        'helix-tour-ask',
-        'toggle',
-    ],
+    'helix-tour': ['helix-before-activate', 'helix-before-close', 'helix-complete', 'helix-tour-ask'],
     'helix-tour-stop': ['helix-tour-ask'],
     'helix-tree': ['helix-activate', 'helix-before-activate', 'helix-select'],
     'helix-tree-item': ['helix-before-close', 'helix-before-open', 'helix-select', 'toggle'],

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/notifications/group/notification-group.d.ts

@@ -19,7 +19,7 @@ import type { CSSResultGroup } from 'lit';
  * that says there is something back there.
  *
  * @since 0.24.0
- * @status experimental
+ * @status stable
  * @category feedback
  * @aliases NotificationSection, FeedGroup
  * @documentation https://fusion.dev/helix/components/notifications

package/dist/notifications/notification/notification.d.ts

@@ -28,7 +28,7 @@ import '../../format-date/index.js';
  * viewport rule would hand it the wide branch.
  *
  * @since 0.1.0
- * @status experimental
+ * @status stable
  * @category feedback
  * @documentation https://fusion.dev/helix/components/notifications
  *

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

@@ -16,7 +16,7 @@ import '../notification/notification.js';
  * holds thousands wants `helix-data-table` with a custom cell.
  *
  * @since 0.1.0
- * @status experimental
+ * @status stable
  * @category feedback
  * @documentation https://fusion.dev/helix/components/notifications
  *

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/speed-dial/item/speed-dial-item.css.js

@@ -10,16 +10,12 @@ border: none;
 color: inherit;
 cursor: pointer;
 display: inline-flex;
-flex-direction: row-reverse;
+flex-direction: var(--_speed-dial-row, row-reverse);
 font: inherit;
 gap: var(--helix-space-sm);
 padding: var(--helix-space-none);
 }
 
-:host-context([data-placement$="-start"]) [part="item"] {
-flex-direction: row;
-}
-
 [part="item"]:disabled {
 cursor: not-allowed;
 opacity: 0.5;

package/dist/speed-dial/item/speed-dial-item.d.ts

@@ -9,7 +9,7 @@ import type { CSSResultGroup } from 'lit';
  * over. Everything about choosing it is the base class.
  *
  * @since 0.1.0
- * @status experimental
+ * @status stable
  * @category actions
  * @aliases Speed dial action, FAB action, Quick action
  * @documentation https://fusion.dev/helix/components/speed-dial

package/dist/speed-dial/root/speed-dial-root.css.js

@@ -15,10 +15,14 @@ padding: var(--helix-space-none);
 }
 
 [part="actions"] {
+--_speed-dial-row: row-reverse;
+
 align-items: flex-end;
 }
 
 [part="actions"][data-placement$="-start"] {
+--_speed-dial-row: row;
+
 align-items: flex-start;
 }
 

package/dist/speed-dial/root/speed-dial-root.d.ts

@@ -10,7 +10,7 @@ import '../../icon/index.js';
  * moves through it is the base class.
  *
  * @since 0.1.0
- * @status experimental
+ * @status stable
  * @category actions
  * @aliases FAB, Floating action button, Action button, Quick actions
  * @documentation https://fusion.dev/helix/components/speed-dial

package/dist/toast/item/toast-item.d.ts

@@ -10,7 +10,7 @@ import type { CSSResultGroup } from 'lit';
  * costs contrast for something the mark already says.
  *
  * @since 0.1.0
- * @status experimental
+ * @status stable
  * @documentation https://fusion.dev/helix/components/toast
  *
  * @cssproperty --toast-border-color - Color of the panel's edge.

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

@@ -18,9 +18,9 @@ import type { CSSResultGroup } from 'lit';
  * into the top layer.
  *
  * @since 0.1.0
- * @status experimental
+ * @status stable
  * @category overlays
- * @aliases Toaster, Snackbar, Notifications
+ * @aliases Toaster, Snackbar
  * @documentation https://fusion.dev/helix/components/toast
  *
  * @cssproperty --toast-gap - Space between one message and the next.

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.
  *