@fusion.dev/helix 0.52.0 → 0.53.0

package/types/vue.d.ts

@@ -340,10 +340,9 @@ export type HelixAnnouncementVueProps = {
 it up to the surface step, for a band that reads as part of the furniture
 rather than as a slot cut into it.
 
-**This was `tone="surface"`**, which put an elevation on the axis that says
-what a thing means. The band's own doc admitted it, calling `surface` the
-one value that was not a color. A band can be `info` and elevated at the
-same time, and two values that can both be true are two axes.
+**`separation` and not `tone`, because a rung is not a meaning.** A band
+can be `info` and elevated at the same time, and two values that can both
+be true are two axes, which is the test the registry answers to.
 
 Styled and not headless, because a rung of a ladder is paint: the headless
 tier has no stylesheet to sit a band on. `tone` crosses because meaning
@@ -514,7 +513,14 @@ can draw a part as less than nothing, `step` is for a quantity that changes
 at a moment and is ordered the way `straight` is.
 
 Absent rather than defaulted because a reflecting property with a default
-writes its attribute onto every host, including the ones nobody configured. */
+writes its attribute onto every host, including the ones nobody configured.
+The resting value therefore lives in the render, as `curve ?? 'straight'`.
+
+**`LineChart` and `Sparkline` rest at `smooth` and are not disagreeing.** A
+line claims a position, so the bounded invention a monotone cubic makes is
+a reading aid and costs nothing. A band claims an amount, and two sums
+smoothed independently can cross, so the same aid here draws a part as less
+than nothing. Same axis, different mark, different resting value. */
   curve?: (HelixAreaChart["curve"]) | undefined;
   /** Which rules are drawn across the plot, if any.
 
@@ -5256,7 +5262,13 @@ renders, including the ones nobody configured.
 consumer wrote. The default therefore lives where the path is built, as
 `curve ?? 'smooth'`.
 
-`step` claims the opposite of both, that a reading holds until the next. */
+`step` claims the opposite of both, that a reading holds until the next.
+
+**`AreaChart` rests at `straight` and is not disagreeing.** A line claims a
+position and a stacked band claims an amount: a curve fitted through one
+sum can pass under the curve fitted through the sum beneath it, so a
+smoothed stack can draw a part as less than nothing. There is no such edge
+here, which is what lets a line take the reading aid. */
   curve?: (HelixLineChart["curve"]) | undefined;
   /** Which rules are drawn across the plot, if any.
 
@@ -5822,8 +5834,10 @@ the loudest thing in the region. The case is a dashboard of several meters
 where one is the number being watched and the rest are context, which is a
 fact about the region rather than about any one of them.
 
-**One value and not the four.** `ghost` would leave a track with nothing in
-it, which is not a quiet reading but an absent one. `outlined` earns its
+**One value of the five.** `ghost` would leave a track with nothing in
+it, which is not a quiet reading but an absent one. `muted` is the quiet
+ink `Text` takes and a reading draws a fill rather than ink, so `subtle` is
+the whole of what quiet means here. `outlined` earns its
 place in `BarChart`, which keeps the area and fades it toward the page, only
 because a chart has other series for the outlined one to be a *different
 kind of fact from* (a forecast, a target, a budget). A meter reports one
@@ -6021,6 +6035,22 @@ separated.** A consumer wanting the whole feed carded says so once, in a
 document rule on the element, rather than on every item: this is a styled
 axis and a stylesheet is where it is set. */
   separation?: (HelixNotification["separation"]) | undefined;
+  /** Whether it offers a control to take it away. */
+  dismissible?: (HelixNotification["dismissible"]) | undefined;
+  /** Accessible name for that control.
+
+`attribute` is spelled out because Lit lowercases a property name to
+derive one rather than dash-casing it, so this would otherwise be
+reachable only as `dismisslabel`, which nobody would guess and no linter
+would catch. */
+  "dismiss-label"?: (HelixNotification["dismissLabel"]) | undefined;
+  /** Accessible name for that control.
+
+`attribute` is spelled out because Lit lowercases a property name to
+derive one rather than dash-casing it, so this would otherwise be
+reachable only as `dismisslabel`, which nobody would guess and no linter
+would catch. */
+  dismissLabel?: (HelixNotification["dismissLabel"]) | undefined;
   /** When it happened, as anything `Date` parses.
 
 An ISO string is what an API sends and what `<time datetime>` takes, so it
@@ -6046,12 +6076,6 @@ declaration. `:state(read)` is what the stylesheet reads.
   "default-read"?: (HelixNotification["defaultRead"]) | undefined;
   /** State to open with, where nothing declared one. */
   defaultRead?: (HelixNotification["defaultRead"]) | undefined;
-  /** Whether a reader may remove it. */
-  dismissible?: (HelixNotification["dismissible"]) | undefined;
-  /** Accessible name for the dismiss control. */
-  "dismiss-label"?: (HelixNotification["dismissLabel"]) | undefined;
-  /** Accessible name for the dismiss control. */
-  dismissLabel?: (HelixNotification["dismissLabel"]) | undefined;
   /** Locale for the timestamp.
 
 Empty is the runtime's own. */
@@ -6443,7 +6467,7 @@ the name of the tool being run, or the file being read. */
 
 Reflected because the stylesheet selects on it. The mesh is chosen from the
 rendered box rather than from this, so `--orb-size` and a consumer's own
-`inline-size` get the same treatment as the three named steps. */
+`inline-size` get the same treatment as the named steps. */
   size?: (HelixOrb["size"]) | undefined;
   /** What the agent is doing.
 
@@ -6906,8 +6930,10 @@ export type HelixProgressVueProps = {
 the loudest thing in the region. The case is a background task, which has to
 be visible and must not compete with what the reader is actually looking at.
 
-**One value and not the four.** `ghost` would leave a track with nothing in
-it, which is not a quiet reading but an absent one. `outlined` is the
+**One value of the five.** `ghost` would leave a track with nothing in
+it, which is not a quiet reading but an absent one. `muted` is the quiet
+ink `Text` takes and a bar draws a fill rather than ink, so `subtle` is the
+whole of what quiet means here. `outlined` is the
 interesting refusal: `BarChart` earns it by keeping the area and fading it
 toward the page, so an outlined column still encodes its value and stands as
 a *different kind of fact* from the series beside it (a forecast, a target,
@@ -7005,11 +7031,13 @@ and a URL is a better name than "QR code" for a reader who cannot see it. */
   label?: (HelixQrCode["label"]) | undefined;
   /** How the modules are drawn.
 
-`square` is the default and the only one that joins runs of adjacent
-modules into a single subpath, which is what keeps a thousand modules to a
-handful of nodes. `rounded` and `dots` draw each module on its own, because
-the corners are the thing being drawn and a joined run has none in the
-middle. That cost is paid only by a code that asks for them.
+`square` is the resting state and is written by not writing it, per the
+rule that a reflected property takes no default. It is also the only one
+that joins runs of adjacent modules into a single subpath, which is what
+keeps a thousand modules to a handful of nodes. `rounded` and `dots` draw
+each module on its own, because the corners are the thing being drawn and a
+joined run has none in the middle. That cost is paid only by a code that
+asks for them.
 
 A scanner reads contrast between cells, not their shape, so all three
 scan. `dots` sits a little under half a module so neighbors do not touch,
@@ -7165,13 +7193,15 @@ The circle stays in both. A card whose only marker was its own border would
 ask a reader to compare surfaces across a row to find the answer, and would
 leave nothing for a high-contrast display. */
   variant?: (HelixRadio["variant"]) | undefined;
-  /** Whether this choice can be made. */
+  /** Whether this one can be chosen. */
   disabled?: (HelixRadio["disabled"]) | undefined;
-  /** Whether this is the current choice.
+  /** Whether this is the current one.
 
-Written by the group. */
+Written by the set rather than by a consumer, which is why it takes no
+default from an attribute here: a family whose selection a consumer
+declares in markup carries `defaultSelected` of its own to say so. */
   selected?: (HelixRadio["selected"]) | undefined;
-  /** Identifies this choice to the group, and is what the form submits. */
+  /** Identifies this one to the set, and is what a form submits. */
   value?: (HelixRadio["value"]) | undefined;
   /** Whether the markup declared this one chosen, which is what a reset returns to.
 
@@ -7760,9 +7790,12 @@ inside a sentence.
 **`emphasis` and not `separation`, which the registry decides rather than
 taste.** Emphasis is asked of controls, how loud this one is; separation is
 asked of containers, where the surface ends. A trigger is a control, and a
-family may not declare both. Two of the four values are refused: `solid` and
-`subtle` are a button's way of being the one thing to press, which is not a
-thing an answer should ever be.
+family may not declare both. Three of the five values are refused: `solid`
+and `subtle` are a button's way of being the one thing to press, which is
+not a thing an answer should ever be, and `muted` is the quiet ink `Text`
+takes, where a trigger's loudness is its frame rather than its ink.
+`outlined` is what the unset frame already draws, so writing it would be
+writing the resting state out.
 
 **The other three fields want this too and do not have it yet.** `Input`,
 `Textarea` and `Combobox` wear the same frame from the same shared
@@ -8092,7 +8125,13 @@ assert against. So the resting state is still the attribute's absence, and
 `curve ?? 'smooth'` is what reads it.
 
 `step` claims the opposite of both, that a reading holds until the next.
-Bars ignore it, having no between to interpolate. */
+Bars ignore it, having no between to interpolate.
+
+**`AreaChart` rests at `straight` and is not disagreeing.** A line claims a
+position and a stacked band claims an amount: a curve fitted through one
+sum can pass under the curve fitted through the sum beneath it, so a
+smoothed stack can draw a part as less than nothing. There is no such edge
+here, which is what lets a line take the reading aid. */
   curve?: (HelixSparkline["curve"]) | undefined;
   /** The id of a table to read instead, when there is one behind the line.
 
@@ -8814,11 +8853,15 @@ export type HelixTabHelixSelectElementEvent =
   HelixTabElementEvent<HelixSelectEvent>;
 
 export type HelixTabVueProps = {
-  /** Whether the tab can be chosen. */
+  /** Whether this one can be chosen. */
   disabled?: (HelixTab["disabled"]) | undefined;
-  /** Whether this tab is the current one. */
+  /** Whether this is the current one.
+
+Written by the set rather than by a consumer, which is why it takes no
+default from an attribute here: a family whose selection a consumer
+declares in markup carries `defaultSelected` of its own to say so. */
   selected?: (HelixTab["selected"]) | undefined;
-  /** Identifies the tab, and pairs it with the panel of the same value. */
+  /** Identifies this one to the set, and is what a form submits. */
   value?: (HelixTab["value"]) | undefined;
 };
 
@@ -9671,11 +9714,15 @@ export type HelixToggleHelixSelectElementEvent =
   HelixToggleElementEvent<HelixSelectEvent>;
 
 export type HelixToggleVueProps = {
-  /** Whether the item can be chosen. */
+  /** Whether this one can be chosen. */
   disabled?: (HelixToggle["disabled"]) | undefined;
-  /** Whether this item is the current one. */
+  /** Whether this is the current one.
+
+Written by the set rather than by a consumer, which is why it takes no
+default from an attribute here: a family whose selection a consumer
+declares in markup carries `defaultSelected` of its own to say so. */
   selected?: (HelixToggle["selected"]) | undefined;
-  /** Identifies the item to the group. */
+  /** Identifies this one to the set, and is what a form submits. */
   value?: (HelixToggle["value"]) | undefined;
   /** Whether the markup declared this one chosen, which is what a reset returns to.