@fusion.dev/helix-headless 0.229.0 → 0.230.0

package/types/vue.d.ts

@@ -1326,6 +1326,13 @@ the board can draw. */
   "readonly"?: HelixHeadlessCanvasEdge["readOnly"] | undefined;
   /** Prevents the connection from being removed. */
   "readOnly"?: HelixHeadlessCanvasEdge["readOnly"] | undefined;
+  /** How the line is drawn: `dashed` or `dotted`. Unset is solid.
+
+**A stroke rather than an axis**, which is what the registry keeps it for:
+no other family draws a line whose stroke says something, and a dashed
+connection is the ordinary way to draw a weaker or an optional one. On the
+headless tier because the board that draws the line is. */
+  "stroke"?: HelixHeadlessCanvasEdge["stroke"] | undefined;
   /** The name of the card the connection ends at. */
   "to"?: HelixHeadlessCanvasEdge["to"] | undefined;
   /** The marker at the end of the connection. Unset is an arrow, as JSON Canvas specifies. */
@@ -1343,13 +1350,6 @@ board carries the value across from where it was written. */
   "to-side"?: HelixHeadlessCanvasEdge["toSide"] | undefined;
   /** The side of the `to` card the connection arrives at, when the document sets one. */
   "toSide"?: HelixHeadlessCanvasEdge["toSide"] | undefined;
-  /** How the line is drawn: `dashed` or `dotted`. Unset is solid.
-
-**A variant rather than an axis**, which is what the registry keeps it for:
-no other family draws a line whose stroke says something, and a dashed
-connection is the ordinary way to draw a weaker or an optional one. On the
-headless tier because the board that draws the line is. */
-  "variant"?: HelixHeadlessCanvasEdge["variant"] | undefined;
 };
 
 export type HelixHeadlessCanvasEdgeVueEvents = {
@@ -2804,6 +2804,12 @@ A block with no `label` is named by it, in the header and on the copy
 button, as a docs site names a snippet by its language. Absent hands
 `highlight` an empty string and names nothing. */
   "language"?: HelixHeadlessCodeBlock["language"] | undefined;
+  /** How a diff's two versions are arranged. It has no effect without `diff`.
+
+Absent is unified, each removal above its replacement, which fits any
+width. `split` sets the old version beside the new one. Optional rather
+than defaulted, so the host carries no attribute the consumer did not write. */
+  "layout"?: HelixHeadlessCodeBlock["layout"] | undefined;
   /** Whether the lines are numbered in a gutter beside the code.
 
 The numbers are hidden from the accessibility tree and are not part of a
@@ -2851,12 +2857,6 @@ diff with `context-lines`. `{count}` is how many. */
   "show-unchanged-label"?: HelixHeadlessCodeBlock["showUnchangedLabel"] | undefined;
   /** The words of a button that shows a folded run of unchanged lines, in a diff with `context-lines`. `{count}` is how many. */
   "showUnchangedLabel"?: HelixHeadlessCodeBlock["showUnchangedLabel"] | undefined;
-  /** How a diff's two versions are arranged. It has no effect without `diff`.
-
-Absent is unified, each removal above its replacement, which fits any
-width. `split` sets the old version beside the new one. Optional rather
-than defaulted, so the host carries no attribute the consumer did not write. */
-  "variant"?: HelixHeadlessCodeBlock["variant"] | undefined;
   /** Whether long lines wrap. Without it they scroll.
 
 Off by default, so long lines scroll, because a line break can be
@@ -3415,16 +3415,12 @@ Date Input and Time Input. */
   "readOnly"?: HelixHeadlessColorInput["readOnly"] | undefined;
   /** Colors offered under the picker, as a comma-separated list. */
   "swatches"?: HelixHeadlessColorInput["swatches"] | undefined;
-  /** What the swatch says in `variant="swatch"`, after the field's label, once
+  /** What the swatch says in `trigger="swatch"`, after the field's label, once
 there is a color. `{name}` is the color's name, such as "vibrant red", and
 `{value}` the value as written. */
   "swatch-label"?: HelixHeadlessColorInput["swatchLabel"] | undefined;
-  /** What the swatch says in `variant="swatch"`, after the field's label, once there is a color. `{name}` is the color's name, such as "vibrant red", and `{value}` the value as written. */
+  /** What the swatch says in `trigger="swatch"`, after the field's label, once there is a color. `{name}` is the color's name, such as "vibrant red", and `{value}` the value as written. */
   "swatchLabel"?: HelixHeadlessColorInput["swatchLabel"] | undefined;
-  /** Accessible name for the control that opens the panel. */
-  "trigger-label"?: HelixHeadlessColorInput["triggerLabel"] | undefined;
-  /** Accessible name for the control that opens the panel. */
-  "triggerLabel"?: HelixHeadlessColorInput["triggerLabel"] | undefined;
   /** Whether the field is a text box with a swatch on it, or only the swatch.
 
 `swatch` is the native control's shape: a block of color that opens a
@@ -3440,7 +3436,11 @@ readable and typeable exactly once, in whichever of the two is present.
 The trade is real and is the reason this is not the default: a swatch cannot
 be read or pasted into without opening the panel, which is worse for a form
 where the color is the answer rather than a setting. */
-  "variant"?: HelixHeadlessColorInput["variant"] | undefined;
+  "trigger"?: HelixHeadlessColorInput["trigger"] | undefined;
+  /** Accessible name for the control that opens the panel. */
+  "trigger-label"?: HelixHeadlessColorInput["triggerLabel"] | undefined;
+  /** Accessible name for the control that opens the panel. */
+  "triggerLabel"?: HelixHeadlessColorInput["triggerLabel"] | undefined;
   /** Draws the panel's hue as a wheel around the square, in place of the hue
 ramp. See Color Picker's `wheel`. */
   "wheel"?: HelixHeadlessColorInput["wheel"] | undefined;
@@ -10775,6 +10775,27 @@ trigger to the panel. The attribute also takes a CSS time, such as `0.2s`. */
   "closeDelay"?: HelixHeadlessMegamenu["closeDelay"] | `${number}` | undefined;
   /** The section's name, used for the default trigger and the panel. */
   "label"?: HelixHeadlessMegamenu["label"] | undefined;
+  /** Whether the panel is a card under the trigger or a band across the page.
+
+The resting one is the card, hanging off the trigger and as wide as it
+needs to be. `band` is the other shape navigations use: a run from edge to
+edge under the header, with its contents held to the page's own measure, so
+a set of destinations too wide to sit under one word gets the whole width
+to lay out in.
+
+**A band and not a width, which is why the word is not `full`.** It changes
+where the panel goes as well as how wide it is, which is why this tier
+knows about it at all: a band spans the viewport, so there is nothing to
+measure it against and nothing to flip or shift to, and the placing pass is
+told not to run. Everything else the popover gives, the top layer and the
+dismissal, is exactly what such a band needs. `full` is the registry's word
+for a width, and `Button` and `Dialog` are the two families answering that
+question; borrowing it here would put a third meaning on it.
+
+`layout` and not an axis, for the reason the registry gives: a card under
+a word and a band under a header are two arrangements this family has, and
+no other family is being asked the same question. */
+  "layout"?: HelixHeadlessMegamenu["layout"] | undefined;
   /** How long a pointer rests on the trigger before the panel opens, in
 milliseconds, under `open-on="hover"`. A pointer crossing the bar on its
 way somewhere else opens nothing. The attribute also takes a CSS time, such
@@ -10796,27 +10817,6 @@ heavy enough that opening it on the way past is rude. */
 moves if that side does not fit. A band ignores it, since a band spans the
 page under its bar. */
   "placement"?: HelixHeadlessMegamenu["placement"] | undefined;
-  /** Whether the panel is a card under the trigger or a band across the page.
-
-The resting one is the card, hanging off the trigger and as wide as it
-needs to be. `band` is the other shape navigations use: a run from edge to
-edge under the header, with its contents held to the page's own measure, so
-a set of destinations too wide to sit under one word gets the whole width
-to lay out in.
-
-**A band and not a width, which is why the word is not `full`.** It changes
-where the panel goes as well as how wide it is, which is why this tier
-knows about it at all: a band spans the viewport, so there is nothing to
-measure it against and nothing to flip or shift to, and the placing pass is
-told not to run. Everything else the popover gives, the top layer and the
-dismissal, is exactly what such a band needs. `full` is the registry's word
-for a width, and `Button` and `Dialog` are the two families answering that
-question; borrowing it here would put a third meaning on it.
-
-`variant` and not an axis, for the reason the registry gives: a card under
-a word and a band under a header are two arrangements this family has, and
-no other family is being asked the same question. */
-  "variant"?: HelixHeadlessMegamenu["variant"] | undefined;
   /** Whether the element starts open. Ignored once `open` is written. */
   "default-open"?: HelixHeadlessMegamenu["defaultOpen"] | undefined;
   /** Whether the element starts open. Ignored once `open` is written. */
@@ -11318,10 +11318,6 @@ second "Main".
 
 Empty by default, which leaves the name to `fallbackLabel`. */
   "label"?: HelixHeadlessNavigation["label"] | undefined;
-  /** Stacks the destinations in a column, for a sidebar, where unset is a row
-for a header or a footer. The marker follows the current destination down
-the column as it does along the row. */
-  "orientation"?: HelixHeadlessNavigation["orientation"] | undefined;
   /** How the destinations are drawn, with `Tabs`' three values and for the same
 reasons.
 
@@ -11341,7 +11337,11 @@ column's inline end.
 
 Reflected and left unset by default, so the host carries nothing a
 consumer's server markup does not already have. */
-  "variant"?: HelixHeadlessNavigation["variant"] | undefined;
+  "marker"?: HelixHeadlessNavigation["marker"] | undefined;
+  /** Stacks the destinations in a column, for a sidebar, where unset is a row
+for a header or a footer. The marker follows the current destination down
+the column as it does along the row. */
+  "orientation"?: HelixHeadlessNavigation["orientation"] | undefined;
 };
 
 export type HelixHeadlessNavigationVueEvents = {
@@ -12163,6 +12163,15 @@ slot names it in place of this.
 
 Empty by default, which leaves the name to `fallbackLabel`. */
   "label"?: HelixHeadlessOutline["label"] | undefined;
+  /** The rail form: a slim column of ticks, one per link, that opens on hover,
+focus, or a tap into a surface holding the links.
+
+A marker because no registered axis (emphasis, material, nesting,
+orientation, separation, shape, size, tone, width) has a value for it, and
+a rail is an arrangement of this family alone, as Megamenu's
+`marker="band"` is. It has no default: the outline without it is the list
+of links. */
+  "marker"?: HelixHeadlessOutline["marker"] | undefined;
   /** Which links are marked. `reading` marks the one section being read, the
 last whose heading has passed the reading line. `visible` marks every
 section with part of it on screen, and the mark runs across their links. */
@@ -12175,15 +12184,6 @@ The reading line. A page with a sticky masthead sets this to its height, or
 a little more: without it the current section changes as a heading slides
 under the chrome rather than as it reaches the top of what can be seen. */
   "offset"?: HelixHeadlessOutline["offset"] | undefined;
-  /** The rail form: a slim column of ticks, one per link, that opens on hover,
-focus, or a tap into a surface holding the links.
-
-A variant because no registered axis (emphasis, material, nesting,
-orientation, separation, shape, size, tone, width) has a value for it, and
-a rail is an arrangement of this family alone, as Megamenu's
-`variant="band"` is. It has no default: the outline without it is the list
-of links. */
-  "variant"?: HelixHeadlessOutline["variant"] | undefined;
 };
 
 export type HelixHeadlessOutlineVueEvents = {
@@ -14105,6 +14105,38 @@ height. */
   "grow-again"?: HelixHeadlessSpatialBarChart["growAgain"] | undefined;
   /** Grows the bars again each time the chart comes back into view after it left it, as a pane does when it is opened again, where `grow` alone grows them the first time only. Only a chart that grows takes it. */
   "growAgain"?: HelixHeadlessSpatialBarChart["growAgain"] | undefined;
+  /** How the bars stand.
+
+Unset, they stand on a grid of categories across and series in depth,
+in a box the camera looks at from a corner, so the grid recedes at an
+angle. `row` lays the categories in a straight line across the page and
+turns each bar to the camera, showing its top and two sides, for one row
+of readings in a small space such as a pane: turning the view turns each
+bar where it stands, and the row stays level. It is the chart's own
+drawing that lays the row: a renderer connected through
+`@fusion.dev/helix-plot` stands the bars on the grid.
+
+`diagonal` is the same row climbing to the right as it recedes, each
+place a step further back than the one before, as a row of days on a
+product's page is drawn: the row rises one part in five across the page
+from any turn, and its floor and names climb with it. A row whose bars
+have a size climbs at most a quarter of the plot's height, so the bars
+of a long row keep theirs.
+
+**A row draws its floor in place of a box**: each place as an outline a
+little wider than its bar, and each category's name under it, as many
+names as fit without touching. A name whose bar names a tone is written
+first, in that tone. `no-box` leaves the floor and the names out.
+
+**A `column-gap` on the `fallback` part gives a row's bars one width**,
+which the styled tier sets from `--spatial-bar-chart-bar-size`: one bar
+stands as wide as each of twenty, the row is as long as its bars and
+centered, the tallest bar stands as high as the plot has room for and
+no taller than the row is long and a quarter again, so one bar stands
+as a block, and `fits` says how many bars the plot holds, so a page
+can give it the latest of a longer table. It is read when the plot's
+size changes. */
+  "layout"?: HelixHeadlessSpatialBarChart["layout"] | undefined;
   /** Draws no box: no edges, grid, numbers, or names, and in a `row` no
 floor, so the readings stand alone and fill the plot, as a picture on a
 product's own page does. The
@@ -14137,38 +14169,6 @@ and `{low}` and `{high}` the lowest and the highest value. */
   "summary-label"?: HelixHeadlessSpatialBarChart["summaryLabel"] | undefined;
   /** The `summary` part's sentence. `{count}`, `{series}`, and `{categories}` are the number of bars, series, and categories, written in the locale, and `{low}` and `{high}` the lowest and the highest value. */
   "summaryLabel"?: HelixHeadlessSpatialBarChart["summaryLabel"] | undefined;
-  /** How the bars stand.
-
-Unset, they stand on a grid of categories across and series in depth,
-in a box the camera looks at from a corner, so the grid recedes at an
-angle. `row` lays the categories in a straight line across the page and
-turns each bar to the camera, showing its top and two sides, for one row
-of readings in a small space such as a pane: turning the view turns each
-bar where it stands, and the row stays level. It is the chart's own
-drawing that lays the row: a renderer connected through
-`@fusion.dev/helix-plot` stands the bars on the grid.
-
-`diagonal` is the same row climbing to the right as it recedes, each
-place a step further back than the one before, as a row of days on a
-product's page is drawn: the row rises one part in five across the page
-from any turn, and its floor and names climb with it. A row whose bars
-have a size climbs at most a quarter of the plot's height, so the bars
-of a long row keep theirs.
-
-**A row draws its floor in place of a box**: each place as an outline a
-little wider than its bar, and each category's name under it, as many
-names as fit without touching. A name whose bar names a tone is written
-first, in that tone. `no-box` leaves the floor and the names out.
-
-**A `column-gap` on the `fallback` part gives a row's bars one width**,
-which the styled tier sets from `--spatial-bar-chart-bar-size`: one bar
-stands as wide as each of twenty, the row is as long as its bars and
-centered, the tallest bar stands as high as the plot has room for and
-no taller than the row is long and a quarter again, so one bar stands
-as a block, and `fits` says how many bars the plot holds, so a page
-can give it the latest of a longer table. It is read when the plot's
-size changes. */
-  "variant"?: HelixHeadlessSpatialBarChart["variant"] | undefined;
   /** The words shown in place of the drawing when the table has no readings,
 and the fallback of the `empty` slot. */
   "empty-text"?: HelixHeadlessSpatialBarChart["emptyText"] | undefined;
@@ -15584,6 +15584,17 @@ Empty by default, which leaves the name to `fallbackLabel`. */
   /** Whether a reader has to finish each stage, or pass an `optional` one,
 before going on to the next. */
   "linear"?: HelixHeadlessSteps["linear"] | undefined;
+  /** What each step is marked with.
+
+Absent is the state itself: a check where a stage is done, a target where
+the reader is, an empty ring ahead of them. Three marks that need no
+legend, which a number does: "3" says where a stage sits in the order and
+nothing about whether it is finished.
+
+`numeric` is the older convention and is still the right one where the
+order is the point, a form that says "step 3 of 5" beside it, or a sequence
+a reader is told to come back to by number. */
+  "marker"?: HelixHeadlessSteps["marker"] | undefined;
   /** Which way the steps run.
 
 Absent is a row, which is what a form header wants, with each name under
@@ -15603,17 +15614,6 @@ number, for a sentence that places the sign itself. */
   "progress-label"?: HelixHeadlessSteps["progressLabel"] | undefined;
   /** What the `progress` part says to a screen reader. `{share, number, percent}` writes `progress` as a percentage the way the locale writes one, such as `40%`, or `40 %` in French. `{percent}` is `progress` as a whole number, for a sentence that places the sign itself. */
   "progressLabel"?: HelixHeadlessSteps["progressLabel"] | undefined;
-  /** What each step is marked with.
-
-Absent is the state itself: a check where a stage is done, a target where
-the reader is, an empty ring ahead of them. Three marks that need no
-legend, which a number does: "3" says where a stage sits in the order and
-nothing about whether it is finished.
-
-`numeric` is the older convention and is still the right one where the
-order is the point, a form that says "step 3 of 5" beside it, or a sequence
-a reader is told to come back to by number. */
-  "variant"?: HelixHeadlessSteps["variant"] | undefined;
   /** The `value` of the current item.
 
 Not `option.active`, which is the option the keyboard is on: that is a
@@ -16281,16 +16281,6 @@ Automatic is the default because showing a panel is usually cheap. Set this
 where it is not, so a reader arrowing past four tabs does not load four
 panels on the way. */
   "manual"?: HelixHeadlessTabs["manual"] | undefined;
-  /** The direction the tabs run. `vertical` sets them in a column beside the
-panels and tells a screen reader the list is vertical.
-
-Optional, so the resting row writes no attribute onto the host. */
-  "orientation"?: HelixHeadlessTabs["orientation"] | undefined;
-  /** Whether a strip with more tabs than fit shows a button at each end it can
-scroll toward. */
-  "scroll-controls"?: HelixHeadlessTabs["scrollControls"] | undefined;
-  /** Whether a strip with more tabs than fit shows a button at each end it can scroll toward. */
-  "scrollControls"?: HelixHeadlessTabs["scrollControls"] | undefined;
   /** How the row of tabs is drawn.
 
 Unset is a raised pill on the selected tab with nothing behind the row,
@@ -16313,7 +16303,17 @@ away.
 
 Reflected and left unset by default, so the host carries nothing a
 consumer's server markup does not already have. */
-  "variant"?: HelixHeadlessTabs["variant"] | undefined;
+  "marker"?: HelixHeadlessTabs["marker"] | undefined;
+  /** The direction the tabs run. `vertical` sets them in a column beside the
+panels and tells a screen reader the list is vertical.
+
+Optional, so the resting row writes no attribute onto the host. */
+  "orientation"?: HelixHeadlessTabs["orientation"] | undefined;
+  /** Whether a strip with more tabs than fit shows a button at each end it can
+scroll toward. */
+  "scroll-controls"?: HelixHeadlessTabs["scrollControls"] | undefined;
+  /** Whether a strip with more tabs than fit shows a button at each end it can scroll toward. */
+  "scrollControls"?: HelixHeadlessTabs["scrollControls"] | undefined;
   /** The `value` of the current item.
 
 Not `option.active`, which is the option the keyboard is on: that is a
@@ -16948,6 +16948,21 @@ on why a wheel cannot do either. */
   "now-label"?: HelixHeadlessTimeInput["nowLabel"] | undefined;
   /** The words on the list's button that chooses the current time, drawn with `show-now`. */
   "nowLabel"?: HelixHeadlessTimeInput["nowLabel"] | undefined;
+  /** Whether the panel shows one list of times or a column for each part of the
+time.
+
+`list` offers whole times, which is what a product with slots or opening
+hours has. `wheels` splits them into an hour, a minute and a meridiem where
+the locale uses one, which is the only way to reach `23:45` without
+scrolling most of a day. `TimePicker` carries the longer note on the trade.
+
+**Optional rather than defaulted, which is not a style preference.** A
+reflecting property with a default writes its attribute onto every host the
+moment the element upgrades, including the ones a consumer rendered and did
+not touch, and React reads that as a hydration mismatch. The absent
+attribute *is* the list, which the stylesheet reads as the base rule, so
+only the departure has to be named. */
+  "picker"?: HelixHeadlessTimeInput["picker"] | undefined;
   /** Placeholder text shown before a time is entered. */
   "placeholder"?: HelixHeadlessTimeInput["placeholder"] | undefined;
   /** The message shown when a range holds more than two times.
@@ -17017,21 +17032,6 @@ is words for a developer. */
   "unreadable-message"?: HelixHeadlessTimeInput["unreadableMessage"] | undefined;
   /** The message for text that is no time, where `bad-input-message` is not set. `{mode}` is `single`, `range`, or `multiple`, `{example}` is a time written as the field writes one, `2:30 PM` in `en-US` and `14:30` in `de-DE`, and `{shape}` is `HH:mm`, or `HH:mm:ss` with `seconds`. */
   "unreadableMessage"?: HelixHeadlessTimeInput["unreadableMessage"] | undefined;
-  /** Whether the panel shows one list of times or a column for each part of the
-time.
-
-`list` offers whole times, which is what a product with slots or opening
-hours has. `wheels` splits them into an hour, a minute and a meridiem where
-the locale uses one, which is the only way to reach `23:45` without
-scrolling most of a day. `TimePicker` carries the longer note on the trade.
-
-**Optional rather than defaulted, which is not a style preference.** A
-reflecting property with a default writes its attribute onto every host the
-moment the element upgrades, including the ones a consumer rendered and did
-not touch, and React reads that as a hydration mismatch. The absent
-attribute *is* the list, which the stylesheet reads as the base rule, so
-only the departure has to be named. */
-  "variant"?: HelixHeadlessTimeInput["variant"] | undefined;
   /** What a row of segments reports when the field is required and every
 segment is empty, where `value-missing-message` is not set. `{kind}` is
 `date` or `time`. */
@@ -17350,7 +17350,7 @@ behavior and a reader who has met one has met both. The alternative, a
 separate "from" and "to" control, is two answers to what a product asks as
 one, and it makes the between part impossible to show.
 
-**Neither works on wheels and the variant falls back.** A range on
+**Neither works on wheels and the picker falls back.** A range on
 wheels is two sets of wheels, which is two controls; a multiple is a set,
 and a wheel has exactly one value by construction. Rather than draw
 something that cannot say what it holds, `wheels` renders as a list
@@ -17361,6 +17361,32 @@ whenever a mode is set. */
   "now-label"?: HelixHeadlessTimePicker["nowLabel"] | undefined;
   /** The words on the button that chooses the current time, drawn with `show-now`. */
   "nowLabel"?: HelixHeadlessTimePicker["nowLabel"] | undefined;
+  /** Shows the times as one `list`, or as `wheels` with a column for each part
+of the time.
+
+`list` is the default and offers whole times, which is what a product with
+opening hours or slots actually has. `wheels` splits them into an hour, a
+minute and, where the locale uses one, a meridiem: three short columns
+instead of ninety-six rows, and the only way to reach `23:45` without
+scrolling most of a day.
+
+The trade is that a wheel cannot say which *combinations* are on offer. A
+list of half hours from nine to five is seventeen rows and every one of them
+is a time the product has; the same thing as columns is an hour column and a
+minute column, and nothing in either says the two are only valid together.
+The bounds are still enforced, so a reader can be refused after the fact,
+which is worse than not being offered it.
+
+So: `list` where the set is the point, `wheels` where any time is allowed
+and the range is a whole day.
+
+**Optional rather than defaulted, which is not a style preference.** A
+reflecting property with a default writes its attribute onto every host the
+moment the element upgrades, including the ones a consumer rendered and did
+not touch, and React reads that as a hydration mismatch. The absent
+attribute *is* the list, which the stylesheet reads as the base rule, so
+only the departure has to be named. */
+  "picker"?: HelixHeadlessTimePicker["picker"] | undefined;
   /** The validation message for a time after `max`. `{max}` is replaced with
 `max`, written in `locale`. */
   "range-overflow-message"?: HelixHeadlessTimePicker["rangeOverflowMessage"] | undefined;
@@ -17431,32 +17457,6 @@ Anything under five is a thousand rows and wants a field instead. */
   "value-missing-message"?: HelixHeadlessTimePicker["valueMissingMessage"] | undefined;
   /** The validation message for a required time picker with no time chosen. */
   "valueMissingMessage"?: HelixHeadlessTimePicker["valueMissingMessage"] | undefined;
-  /** Shows the times as one `list`, or as `wheels` with a column for each part
-of the time.
-
-`list` is the default and offers whole times, which is what a product with
-opening hours or slots actually has. `wheels` splits them into an hour, a
-minute and, where the locale uses one, a meridiem: three short columns
-instead of ninety-six rows, and the only way to reach `23:45` without
-scrolling most of a day.
-
-The trade is that a wheel cannot say which *combinations* are on offer. A
-list of half hours from nine to five is seventeen rows and every one of them
-is a time the product has; the same thing as columns is an hour column and a
-minute column, and nothing in either says the two are only valid together.
-The bounds are still enforced, so a reader can be refused after the fact,
-which is worse than not being offered it.
-
-So: `list` where the set is the point, `wheels` where any time is allowed
-and the range is a whole day.
-
-**Optional rather than defaulted, which is not a style preference.** A
-reflecting property with a default writes its attribute onto every host the
-moment the element upgrades, including the ones a consumer rendered and did
-not touch, and React reads that as a hydration mismatch. The absent
-attribute *is* the list, which the stylesheet reads as the base rule, so
-only the departure has to be named. */
-  "variant"?: HelixHeadlessTimePicker["variant"] | undefined;
   /** A message under the picker, such as what is wrong with the answer.
 
 While set, the picker is invalid and does not submit, as a field's
@@ -20862,7 +20862,7 @@ export interface HelixVueGlobalComponents {
    * depend on color. Where a removed line is paired with the added line that
    * replaced it, the words each does not share with the other are the `changed`
    * part, so the eye goes to what changed within the line. Each file in the patch is its own block under its own name,
-   * and its copy button copies the new version of the file. `variant="split"`
+   * and its copy button copies the new version of the file. `layout="split"`
    * shows the old version beside the new, each removal opposite its replacement.
    * `context-lines` folds each long run of unchanged lines, keeping that many
    * beside each change, behind a button that shows them and hides them again,
@@ -24027,7 +24027,7 @@ export interface HelixVueGlobalComponents {
    * marked, so `a[aria-current]` and `a[data-depth="2"]` are the hooks for a
    * rule of yours.
    *
-   * **The rail.** `variant="rail"` draws a slim column of ticks at the edge of a
+   * **The rail.** `marker="rail"` draws a slim column of ticks at the edge of a
    * long scroll, one per link, with the section in view drawn longer and a deeper
    * level shorter. Hovering or focusing the rail opens a surface holding the
    * links, each on one line, and Escape closes it. A tap opens it too, and it stays
@@ -25452,6 +25452,10 @@ export interface HelixVueGlobalComponents {
    * the arrow keys, and its controls with Enter or F2. A resizable column has a
    * `separator` on its end edge, moved by dragging or with the arrow keys. In a
    * table with reorderable columns, each column has a grip that the table moves.
+   *
+   * A sortable heading draws two chevrons after its words. The chevron for the
+   * current direction takes the heading's ink, so you can see which columns sort
+   * and which way the table is sorted.
    */
   "helix-headless-table-column": DefineCustomElement<HelixHeadlessTableColumn, HelixHeadlessTableColumnVueProps, HelixHeadlessTableColumnVueEvents>;
   /**
@@ -25895,7 +25899,7 @@ export interface HelixVueGlobalComponents {
    * with `aria-haspopup="dialog"`, `aria-expanded`, and `aria-controls`, since
    * Down opens the list from it. In the list, the arrow keys, typed digits and PageUp and PageDown
    * move through the times, and Enter, Space or a click chooses one and closes
-   * the panel. With `variant="wheels"` each wheel moves the time as you turn it,
+   * the panel. With `picker="wheels"` each wheel moves the time as you turn it,
    * the panel stays open, and Enter or Escape closes it.
    *
    * With `segmented`, the field is a row of segments in place of the text: an
@@ -25930,7 +25934,7 @@ export interface HelixVueGlobalComponents {
   /**
    * Shows the times at each `step` as a `Listbox`, which provides the keyboard
    * behavior, typeahead, scrolling into view, and announcements for a set of
-   * options. `variant="wheels"` shows a column each for the hour, the minute, and
+   * options. `picker="wheels"` shows a column each for the hour, the minute, and
    * the meridiem, and one for the second with `seconds`. Left and Right move
    * between the wheels, and Tab does too.
    *

package/types/words.d.ts

@@ -959,7 +959,7 @@ declare module '@fusion.dev/helix-core' {
     }
     'helix-color-input': {
       /**
-       * What the swatch says in `variant="swatch"`, after the field's label, once
+       * What the swatch says in `trigger="swatch"`, after the field's label, once
        * there is a color. `{name}` is the color's name, such as "vibrant red", and
        * `{value}` the value as written.
        *