@fusion.dev/helix 0.159.0 → 0.160.0

package/types/jsx.d.ts

@@ -11512,6 +11512,9 @@ export type HelixDateInputHelixBeforeCloseElementEvent =
 /** `helix-before-open` event type */
 export type HelixDateInputHelixBeforeOpenElementEvent =
   HelixDateInputElementEvent<HelixBeforeOpenEvent>;
+/** `helix-clear` event type */
+export type HelixDateInputHelixClearElementEvent =
+  HelixDateInputElementEvent<HelixClearEvent>;
 
 export type HelixDateInputProps = {
   /** What a row of segments reports when the field is required and every
@@ -11536,6 +11539,18 @@ are not, where `bad-input-message` is not set. `{kind}` is `date` or
 are not, where `bad-input-message` is not set. `{kind}` is `date` or
 `time`. */
   incompleteMessage?: (HelixDateInput["incompleteMessage"]) | undefined;
+  /** What a screen reader hears before the segments of a range's second date
+or time, after each segment's own name. */
+  "range-end-label"?: (HelixDateInput["rangeEndLabel"]) | undefined;
+  /** What a screen reader hears before the segments of a range's second date
+or time, after each segment's own name. */
+  rangeEndLabel?: (HelixDateInput["rangeEndLabel"]) | undefined;
+  /** What a screen reader hears before the segments of a range's first date
+or time, after each segment's own name: "month, Start, Stay". */
+  "range-start-label"?: (HelixDateInput["rangeStartLabel"]) | undefined;
+  /** What a screen reader hears before the segments of a range's first date
+or time, after each segment's own name: "month, Start, Stay". */
+  rangeStartLabel?: (HelixDateInput["rangeStartLabel"]) | undefined;
   /** Whether the field is a row of segments, one for each part of the date or
 time, in place of a line of text.
 
@@ -11700,32 +11715,48 @@ and this one was the English a form in another language still spoke in
 the bubble it raises on submit: `feedback` replaces the message under
 the field and does not reach that one. */
   valueMissingMessage?: (HelixDateInput["valueMissingMessage"]) | undefined;
-  /** What the browser may autofill here, as one of the platform's own tokens.
+  /** What the browser may autofill here, as one of the platform's own tokens,
+such as `bday`.
 
 Empty leaves the attribute off, which is the browser's default and is what
 lets autofill work at all: hardcoding `off` here means a birthday or a
-postal code can never be filled in for a reader. */
+postal code can never be filled in for a reader. With `segmented`, a
+hidden native date input carries it, since no browser fills the segments. */
   autocomplete?: (HelixDateInput["autocomplete"]) | undefined;
-  /** The calendar the written date and the calendar's days are in: `gregory`,
-`buddhist`, `japanese`, `roc`, or `iso8601`.
-
-Absent is the locale's own where it is one of the five, and `gregory` for
-every other, as Date Picker's `calendar` is. The value is `YYYY-MM-DD` in
-every calendar, and a focused field is ISO in every calendar. In
-`segmented`, the segments are the Gregorian day, month, and year, in the
-order the locale writes them, or ISO order for `iso8601`. */
+  /** The calendar the written date, the segments, and the calendar's days are
+in: `gregory`, `buddhist`, `japanese`, `roc`, or `iso8601`, or a calendar
+with months of its own that Date Picker's `calendar` names, such as
+`persian`, `hebrew`, `islamic-umalqura`, `ethiopic`, or `chinese`.
+
+Absent is the locale's own where its months are the Gregorian months, and
+`gregory` for every other, as Date Picker's `calendar` is. The value is
+`YYYY-MM-DD` in every calendar, and a focused text field is ISO in every
+calendar. In `segmented`, the segments are the day, month, and year as
+the calendar counts them, in the order the locale writes them: Mehr 14,
+1405 is month 7 and day 14 of 1405 under `persian`. Under the five with
+Gregorian months they are the Gregorian day, month, and year, or ISO order
+for `iso8601`. */
   calendar?: (HelixDateInput["calendar"]) | undefined;
   /** The name of the calendar's grid of days, read by screen readers. */
   "calendar-label"?: (HelixDateInput["calendarLabel"]) | undefined;
   /** The name of the calendar's grid of days, read by screen readers. */
   calendarLabel?: (HelixDateInput["calendarLabel"]) | undefined;
+  /** Whether the field shows a button that empties it, as Input's `clearable`
+does. Shown only while the field holds something to clear and is neither
+disabled nor read-only. */
+  clearable?: (HelixDateInput["clearable"]) | undefined;
+  /** The accessible name of the clear button, which shows only an icon. */
+  "clear-label"?: (HelixDateInput["clearLabel"]) | undefined;
+  /** The accessible name of the clear button, which shows only an icon. */
+  clearLabel?: (HelixDateInput["clearLabel"]) | undefined;
   /** How a date is written in the field: `short` through `full`, or ISO.
 
 **The field renders when it is idle and holds the value when it is being
 edited.** A written date is a rendering, and a document being edited must
 not be a rendering of something else: `Intl.DateTimeFormat` formats and does
-not parse, so `4 August 2026` cannot be typed back, and writing a parser per
-locale is how a field ends up rejecting what it just displayed.
+not parse, so a rendering such as `Tuesday, August 4, 2026` is no text to
+edit. The field does read a date typed in the locale's order and digits as
+you leave it, which covers what a reader types.
 
 The way out is not to choose between the two but to separate them in time.
 Idle, the field shows `4 August 2026`, which is what a date is for reading.
@@ -11747,8 +11778,9 @@ submits and what `min` and `max` compare against. */
 **The field renders when it is idle and holds the value when it is being
 edited.** A written date is a rendering, and a document being edited must
 not be a rendering of something else: `Intl.DateTimeFormat` formats and does
-not parse, so `4 August 2026` cannot be typed back, and writing a parser per
-locale is how a field ends up rejecting what it just displayed.
+not parse, so a rendering such as `Tuesday, August 4, 2026` is no text to
+edit. The field does read a date typed in the locale's order and digits as
+you leave it, which covers what a reader types.
 
 The way out is not to choose between the two but to separate them in time.
 Idle, the field shows `4 August 2026`, which is what a date is for reading.
@@ -11886,6 +11918,14 @@ the date.
 **The name goes in**, so a row of them is heard as which one each
 removes rather than as "Remove" said once per date. */
   removeLabel?: (HelixDateInput["removeLabel"]) | undefined;
+  /** What a screen reader hears about the dates chosen in the calendar, with
+`{kind}`, `{start}`, `{end}` and `{count}` filled in as Date Picker's
+`selection-label` says. */
+  "selection-label"?: (HelixDateInput["selectionLabel"]) | undefined;
+  /** What a screen reader hears about the dates chosen in the calendar, with
+`{kind}`, `{start}`, `{end}` and `{count}` filled in as Date Picker's
+`selection-label` says. */
+  selectionLabel?: (HelixDateInput["selectionLabel"]) | undefined;
   /** How far apart the selectable dates are, in days.
 
 `<input type="date" step>`'s own unit, handed to the calendar this renders
@@ -11897,6 +11937,14 @@ platform's base. */
   "step-mismatch-message"?: (HelixDateInput["stepMismatchMessage"]) | undefined;
   /** The message shown when a date is not on `step`. */
   stepMismatchMessage?: (HelixDateInput["stepMismatchMessage"]) | undefined;
+  /** The time zone today is read in, such as `America/New_York`, handed to the
+calendar: the day marked today, and the month an empty field opens on.
+Empty is the reader's own. Dates are plain `YYYY-MM-DD` and carry no zone. */
+  "time-zone"?: (HelixDateInput["timeZone"]) | undefined;
+  /** The time zone today is read in, such as `America/New_York`, handed to the
+calendar: the day marked today, and the month an empty field opens on.
+Empty is the reader's own. Dates are plain `YYYY-MM-DD` and carry no zone. */
+  timeZone?: (HelixDateInput["timeZone"]) | undefined;
   /** The name of the button that opens the calendar, read by screen readers. */
   "trigger-label"?: (HelixDateInput["triggerLabel"]) | undefined;
   /** The name of the button that opens the calendar, read by screen readers. */
@@ -11905,6 +11953,12 @@ platform's base. */
   "unavailable-message"?: (HelixDateInput["unavailableMessage"]) | undefined;
   /** The message shown when `disable-dates` or `disable-days` bars a date. */
   unavailableMessage?: (HelixDateInput["unavailableMessage"]) | undefined;
+  /** The message for text that is no date, where `bad-input-message` is not
+set. `{mode}` is `single`, `range`, or `multiple`. */
+  "unreadable-message"?: (HelixDateInput["unreadableMessage"]) | undefined;
+  /** The message for text that is no date, where `bad-input-message` is not
+set. `{mode}` is `single`, `range`, or `multiple`. */
+  unreadableMessage?: (HelixDateInput["unreadableMessage"]) | undefined;
   /** The name of the calendar's heading where it shows a page of years, with
 `{heading}` filled in. */
   "year-view-label"?: (HelixDateInput["yearViewLabel"]) | undefined;
@@ -11976,6 +12030,8 @@ reader makes in one of these. */
   "onhelix-before-open"?: ((
     e: HelixDateInputHelixBeforeOpenElementEvent,
   ) => void) | undefined;
+  /** Fired after the clear button has emptied the field, after `input` and `change`. */
+  "onhelix-clear"?: ((e: HelixDateInputHelixClearElementEvent) => void) | undefined;
   /** Fired after the value changes. */
   oninput?: ((e: HelixDateInputElementEvent) => void) | undefined;
 };
@@ -12003,6 +12059,18 @@ are not, where `bad-input-message` is not set. `{kind}` is `date` or
 are not, where `bad-input-message` is not set. `{kind}` is `date` or
 `time`. */
   "prop:incompleteMessage"?: (HelixDateInput["incompleteMessage"]) | undefined;
+  /** What a screen reader hears before the segments of a range's second date
+or time, after each segment's own name. */
+  "attr:range-end-label"?: (HelixDateInput["rangeEndLabel"]) | undefined;
+  /** What a screen reader hears before the segments of a range's second date
+or time, after each segment's own name. */
+  "prop:rangeEndLabel"?: (HelixDateInput["rangeEndLabel"]) | undefined;
+  /** What a screen reader hears before the segments of a range's first date
+or time, after each segment's own name: "month, Start, Stay". */
+  "attr:range-start-label"?: (HelixDateInput["rangeStartLabel"]) | undefined;
+  /** What a screen reader hears before the segments of a range's first date
+or time, after each segment's own name: "month, Start, Stay". */
+  "prop:rangeStartLabel"?: (HelixDateInput["rangeStartLabel"]) | undefined;
   /** Whether the field is a row of segments, one for each part of the date or
 time, in place of a line of text.
 
@@ -12167,32 +12235,48 @@ and this one was the English a form in another language still spoke in
 the bubble it raises on submit: `feedback` replaces the message under
 the field and does not reach that one. */
   "prop:valueMissingMessage"?: (HelixDateInput["valueMissingMessage"]) | undefined;
-  /** What the browser may autofill here, as one of the platform's own tokens.
+  /** What the browser may autofill here, as one of the platform's own tokens,
+such as `bday`.
 
 Empty leaves the attribute off, which is the browser's default and is what
 lets autofill work at all: hardcoding `off` here means a birthday or a
-postal code can never be filled in for a reader. */
+postal code can never be filled in for a reader. With `segmented`, a
+hidden native date input carries it, since no browser fills the segments. */
   "prop:autocomplete"?: (HelixDateInput["autocomplete"]) | undefined;
-  /** The calendar the written date and the calendar's days are in: `gregory`,
-`buddhist`, `japanese`, `roc`, or `iso8601`.
-
-Absent is the locale's own where it is one of the five, and `gregory` for
-every other, as Date Picker's `calendar` is. The value is `YYYY-MM-DD` in
-every calendar, and a focused field is ISO in every calendar. In
-`segmented`, the segments are the Gregorian day, month, and year, in the
-order the locale writes them, or ISO order for `iso8601`. */
+  /** The calendar the written date, the segments, and the calendar's days are
+in: `gregory`, `buddhist`, `japanese`, `roc`, or `iso8601`, or a calendar
+with months of its own that Date Picker's `calendar` names, such as
+`persian`, `hebrew`, `islamic-umalqura`, `ethiopic`, or `chinese`.
+
+Absent is the locale's own where its months are the Gregorian months, and
+`gregory` for every other, as Date Picker's `calendar` is. The value is
+`YYYY-MM-DD` in every calendar, and a focused text field is ISO in every
+calendar. In `segmented`, the segments are the day, month, and year as
+the calendar counts them, in the order the locale writes them: Mehr 14,
+1405 is month 7 and day 14 of 1405 under `persian`. Under the five with
+Gregorian months they are the Gregorian day, month, and year, or ISO order
+for `iso8601`. */
   "prop:calendar"?: (HelixDateInput["calendar"]) | undefined;
   /** The name of the calendar's grid of days, read by screen readers. */
   "attr:calendar-label"?: (HelixDateInput["calendarLabel"]) | undefined;
   /** The name of the calendar's grid of days, read by screen readers. */
   "prop:calendarLabel"?: (HelixDateInput["calendarLabel"]) | undefined;
+  /** Whether the field shows a button that empties it, as Input's `clearable`
+does. Shown only while the field holds something to clear and is neither
+disabled nor read-only. */
+  "prop:clearable"?: (HelixDateInput["clearable"]) | undefined;
+  /** The accessible name of the clear button, which shows only an icon. */
+  "attr:clear-label"?: (HelixDateInput["clearLabel"]) | undefined;
+  /** The accessible name of the clear button, which shows only an icon. */
+  "prop:clearLabel"?: (HelixDateInput["clearLabel"]) | undefined;
   /** How a date is written in the field: `short` through `full`, or ISO.
 
 **The field renders when it is idle and holds the value when it is being
 edited.** A written date is a rendering, and a document being edited must
 not be a rendering of something else: `Intl.DateTimeFormat` formats and does
-not parse, so `4 August 2026` cannot be typed back, and writing a parser per
-locale is how a field ends up rejecting what it just displayed.
+not parse, so a rendering such as `Tuesday, August 4, 2026` is no text to
+edit. The field does read a date typed in the locale's order and digits as
+you leave it, which covers what a reader types.
 
 The way out is not to choose between the two but to separate them in time.
 Idle, the field shows `4 August 2026`, which is what a date is for reading.
@@ -12214,8 +12298,9 @@ submits and what `min` and `max` compare against. */
 **The field renders when it is idle and holds the value when it is being
 edited.** A written date is a rendering, and a document being edited must
 not be a rendering of something else: `Intl.DateTimeFormat` formats and does
-not parse, so `4 August 2026` cannot be typed back, and writing a parser per
-locale is how a field ends up rejecting what it just displayed.
+not parse, so a rendering such as `Tuesday, August 4, 2026` is no text to
+edit. The field does read a date typed in the locale's order and digits as
+you leave it, which covers what a reader types.
 
 The way out is not to choose between the two but to separate them in time.
 Idle, the field shows `4 August 2026`, which is what a date is for reading.
@@ -12353,6 +12438,14 @@ the date.
 **The name goes in**, so a row of them is heard as which one each
 removes rather than as "Remove" said once per date. */
   "prop:removeLabel"?: (HelixDateInput["removeLabel"]) | undefined;
+  /** What a screen reader hears about the dates chosen in the calendar, with
+`{kind}`, `{start}`, `{end}` and `{count}` filled in as Date Picker's
+`selection-label` says. */
+  "attr:selection-label"?: (HelixDateInput["selectionLabel"]) | undefined;
+  /** What a screen reader hears about the dates chosen in the calendar, with
+`{kind}`, `{start}`, `{end}` and `{count}` filled in as Date Picker's
+`selection-label` says. */
+  "prop:selectionLabel"?: (HelixDateInput["selectionLabel"]) | undefined;
   /** How far apart the selectable dates are, in days.
 
 `<input type="date" step>`'s own unit, handed to the calendar this renders
@@ -12364,6 +12457,14 @@ platform's base. */
   "attr:step-mismatch-message"?: (HelixDateInput["stepMismatchMessage"]) | undefined;
   /** The message shown when a date is not on `step`. */
   "prop:stepMismatchMessage"?: (HelixDateInput["stepMismatchMessage"]) | undefined;
+  /** The time zone today is read in, such as `America/New_York`, handed to the
+calendar: the day marked today, and the month an empty field opens on.
+Empty is the reader's own. Dates are plain `YYYY-MM-DD` and carry no zone. */
+  "attr:time-zone"?: (HelixDateInput["timeZone"]) | undefined;
+  /** The time zone today is read in, such as `America/New_York`, handed to the
+calendar: the day marked today, and the month an empty field opens on.
+Empty is the reader's own. Dates are plain `YYYY-MM-DD` and carry no zone. */
+  "prop:timeZone"?: (HelixDateInput["timeZone"]) | undefined;
   /** The name of the button that opens the calendar, read by screen readers. */
   "attr:trigger-label"?: (HelixDateInput["triggerLabel"]) | undefined;
   /** The name of the button that opens the calendar, read by screen readers. */
@@ -12372,6 +12473,12 @@ platform's base. */
   "attr:unavailable-message"?: (HelixDateInput["unavailableMessage"]) | undefined;
   /** The message shown when `disable-dates` or `disable-days` bars a date. */
   "prop:unavailableMessage"?: (HelixDateInput["unavailableMessage"]) | undefined;
+  /** The message for text that is no date, where `bad-input-message` is not
+set. `{mode}` is `single`, `range`, or `multiple`. */
+  "attr:unreadable-message"?: (HelixDateInput["unreadableMessage"]) | undefined;
+  /** The message for text that is no date, where `bad-input-message` is not
+set. `{mode}` is `single`, `range`, or `multiple`. */
+  "prop:unreadableMessage"?: (HelixDateInput["unreadableMessage"]) | undefined;
   /** The name of the calendar's heading where it shows a page of years, with
 `{heading}` filled in. */
   "attr:year-view-label"?: (HelixDateInput["yearViewLabel"]) | undefined;
@@ -12442,6 +12549,8 @@ reader makes in one of these. */
   "on:helix-before-open"?: ((
     e: HelixDateInputHelixBeforeOpenElementEvent,
   ) => void) | undefined;
+  /** Fired after the clear button has emptied the field, after `input` and `change`. */
+  "on:helix-clear"?: ((e: HelixDateInputHelixClearElementEvent) => void) | undefined;
   /** Fired after the value changes. */
   "on:input"?: ((e: HelixDateInputElementEvent) => void) | undefined;
 
@@ -12516,14 +12625,16 @@ it is one of the five, such as `buddhist` for `th-TH` or `japanese` for
 `ja-JP-u-ca-japanese`, and `gregory` for every other, such as `persian`
 for `fa-IR`.
 
-`persian`, `hebrew`, `islamic-umalqura`, `islamic-civil`, `ethiopic`,
-`coptic`, and `indian` draw a calendar with months of its own, as React
-Aria's calendars do: each grid is one of that calendar's months, the
-Hebrew leap month and Ethiopia's five-day thirteenth month included, and
-Previous, Next and the page keys move by those months. `month` and
+`persian`, `hebrew`, `islamic`, `islamic-umalqura`, `islamic-civil`,
+`islamic-tbla`, `islamic-rgsa`, `ethiopic`, `ethioaa`, `coptic`,
+`indian`, `chinese`, and `dangi` draw a calendar with months of its own,
+as React Aria's calendars do: each grid is one of that calendar's months,
+the Hebrew and Chinese leap months and Ethiopia's five-day thirteenth
+month included, and Previous, Next and the page keys move by those
+months. With `max-view`, the months view shows that calendar's year, of
+twelve or thirteen months, and the years view its years. `month` and
 `helix-navigate` then name a month by its first day, `YYYY-MM-DD`. The
-heading stays text, as the months and years views are drawn in Gregorian
-months only. The value is `YYYY-MM-DD` in every calendar. */
+value is `YYYY-MM-DD` in every calendar. */
   calendar?: (HelixDatePicker["calendar"]) | undefined;
   /** The month to open on when `month` is not set. */
   "default-month"?: (HelixDatePicker["defaultMonth"]) | undefined;
@@ -12670,6 +12781,18 @@ else set needs. */
   readOnly?: (HelixDatePicker["readOnly"]) | undefined;
   /** Stops the form from submitting while no date is chosen. */
   required?: (HelixDatePicker["required"]) | undefined;
+  /** What a screen reader hears about the chosen dates: the grid's
+description, said again whenever the dates change. `{kind}` is `date`,
+`start` while a range holds one end, `range`, or `dates` for `multiple`.
+`{start}` and `{end}` are dates written in `locale`, and `{count}` is how
+many dates are chosen. */
+  "selection-label"?: (HelixDatePicker["selectionLabel"]) | undefined;
+  /** What a screen reader hears about the chosen dates: the grid's
+description, said again whenever the dates change. `{kind}` is `date`,
+`start` while a range holds one end, `range`, or `dates` for `multiple`.
+`{start}` and `{end}` are dates written in `locale`, and `{count}` is how
+many dates are chosen. */
+  selectionLabel?: (HelixDatePicker["selectionLabel"]) | undefined;
   /** How far apart the selectable dates are, in days.
 
 `<input type="date" step>`'s own unit, counted from `min` where there is
@@ -12847,14 +12970,16 @@ it is one of the five, such as `buddhist` for `th-TH` or `japanese` for
 `ja-JP-u-ca-japanese`, and `gregory` for every other, such as `persian`
 for `fa-IR`.
 
-`persian`, `hebrew`, `islamic-umalqura`, `islamic-civil`, `ethiopic`,
-`coptic`, and `indian` draw a calendar with months of its own, as React
-Aria's calendars do: each grid is one of that calendar's months, the
-Hebrew leap month and Ethiopia's five-day thirteenth month included, and
-Previous, Next and the page keys move by those months. `month` and
+`persian`, `hebrew`, `islamic`, `islamic-umalqura`, `islamic-civil`,
+`islamic-tbla`, `islamic-rgsa`, `ethiopic`, `ethioaa`, `coptic`,
+`indian`, `chinese`, and `dangi` draw a calendar with months of its own,
+as React Aria's calendars do: each grid is one of that calendar's months,
+the Hebrew and Chinese leap months and Ethiopia's five-day thirteenth
+month included, and Previous, Next and the page keys move by those
+months. With `max-view`, the months view shows that calendar's year, of
+twelve or thirteen months, and the years view its years. `month` and
 `helix-navigate` then name a month by its first day, `YYYY-MM-DD`. The
-heading stays text, as the months and years views are drawn in Gregorian
-months only. The value is `YYYY-MM-DD` in every calendar. */
+value is `YYYY-MM-DD` in every calendar. */
   "prop:calendar"?: (HelixDatePicker["calendar"]) | undefined;
   /** The month to open on when `month` is not set. */
   "attr:default-month"?: (HelixDatePicker["defaultMonth"]) | undefined;
@@ -13001,6 +13126,18 @@ else set needs. */
   "prop:readOnly"?: (HelixDatePicker["readOnly"]) | undefined;
   /** Stops the form from submitting while no date is chosen. */
   "prop:required"?: (HelixDatePicker["required"]) | undefined;
+  /** What a screen reader hears about the chosen dates: the grid's
+description, said again whenever the dates change. `{kind}` is `date`,
+`start` while a range holds one end, `range`, or `dates` for `multiple`.
+`{start}` and `{end}` are dates written in `locale`, and `{count}` is how
+many dates are chosen. */
+  "attr:selection-label"?: (HelixDatePicker["selectionLabel"]) | undefined;
+  /** What a screen reader hears about the chosen dates: the grid's
+description, said again whenever the dates change. `{kind}` is `date`,
+`start` while a range holds one end, `range`, or `dates` for `multiple`.
+`{start}` and `{end}` are dates written in `locale`, and `{count}` is how
+many dates are chosen. */
+  "prop:selectionLabel"?: (HelixDatePicker["selectionLabel"]) | undefined;
   /** How far apart the selectable dates are, in days.
 
 `<input type="date" step>`'s own unit, counted from `min` where there is
@@ -15947,12 +16084,14 @@ each new line above the one before. */
 
 export type HelixFormatDateProps = {
   /** The calendar a date is written in: `gregory`, `buddhist`, `japanese`,
-`roc`, or `iso8601`, the calendars Date Picker and Date Input draw.
-
-Absent is the locale's own where it is one of the five, such as
-`buddhist` for `th-TH`, and `gregory` for every other, such as `persian`
-for `fa-IR`, so a date written here reads as the same date a Date Picker
-beside it shows. */
+`roc`, or `iso8601`, or a calendar with months of its own, such as
+`persian`, `hebrew`, `islamic-umalqura`, `ethiopic`, or `chinese`: every
+calendar Date Picker and Date Input draw.
+
+Absent is the locale's own where its months are the Gregorian months,
+such as `buddhist` for `th-TH`, and `gregory` for every other, such as
+`persian` for `fa-IR`, so a date written here reads as the same date a
+Date Picker beside it shows. Write `calendar="persian"` for Mehr 14, 1405. */
   calendar?: (HelixFormatDate["calendar"]) | undefined;
   /** The timestamp, in any format `Date` can parse.
 
@@ -15978,6 +16117,14 @@ browser may use either. */
   dateStyle?: (HelixFormatDate["dateStyle"]) | undefined;
   /** How the day of the month is written, where a date is shown. */
   day?: (HelixFormatDate["day"]) | undefined;
+  /** Writes the part of the day in words, such as "in the morning" or "at
+night", in its `long`, `short`, or `narrow` form, where `hour` is on a
+twelve-hour clock. */
+  "day-period"?: (HelixFormatDate["dayPeriod"]) | undefined;
+  /** Writes the part of the day in words, such as "in the morning" or "at
+night", in its `long`, `short`, or `narrow` form, where `hour` is on a
+twelve-hour clock. */
+  dayPeriod?: (HelixFormatDate["dayPeriod"]) | undefined;
   /** Shows how long ago the timestamp was, in a compact form such as "3h", in
 place of the date.
 
@@ -15995,6 +16142,12 @@ Off by default, which draws the date as one run of text, as Shoelace and
 Web Awesome do. An `elapsed` or `relative` reading is one phrase either
 way. */
   fields?: (HelixFormatDate["fields"]) | undefined;
+  /** How many digits of a fraction of a second to write after `second`: 1, 2,
+or 3, as in 09:41:07.250. */
+  "fractional-second-digits"?: (HelixFormatDate["fractionalSecondDigits"]) | undefined;
+  /** How many digits of a fraction of a second to write after `second`: 1, 2,
+or 3, as in 09:41:07.250. */
+  fractionalSecondDigits?: (HelixFormatDate["fractionalSecondDigits"]) | undefined;
   /** Draws an `elapsed` or `relative` reading once and leaves it, where it
 would otherwise move on as it goes stale.
 
@@ -16057,9 +16210,13 @@ Empty is the runtime's own. */
 
 Empty is the runtime's own. */
   timeZone?: (HelixFormatDate["timeZone"]) | undefined;
-  /** Shows the name of the time zone, in its `long` or `short` form. */
+  /** Shows the name of the time zone: `long` or `short`, as Pacific Daylight
+Time or PDT, `longOffset` or `shortOffset`, as GMT-07:00 or GMT-7, or
+`longGeneric` or `shortGeneric`, as Pacific Time or PT. */
   "time-zone-name"?: (HelixFormatDate["timeZoneName"]) | undefined;
-  /** Shows the name of the time zone, in its `long` or `short` form. */
+  /** Shows the name of the time zone: `long` or `short`, as Pacific Daylight
+Time or PDT, `longOffset` or `shortOffset`, as GMT-07:00 or GMT-7, or
+`longGeneric` or `shortGeneric`, as Pacific Time or PT. */
   timeZoneName?: (HelixFormatDate["timeZoneName"]) | undefined;
   /** How the weekday is written, where one is shown. */
   weekday?: (HelixFormatDate["weekday"]) | undefined;
@@ -16069,12 +16226,14 @@ Empty is the runtime's own. */
 
 export type HelixFormatDateSolidJsProps = {
   /** The calendar a date is written in: `gregory`, `buddhist`, `japanese`,
-`roc`, or `iso8601`, the calendars Date Picker and Date Input draw.
-
-Absent is the locale's own where it is one of the five, such as
-`buddhist` for `th-TH`, and `gregory` for every other, such as `persian`
-for `fa-IR`, so a date written here reads as the same date a Date Picker
-beside it shows. */
+`roc`, or `iso8601`, or a calendar with months of its own, such as
+`persian`, `hebrew`, `islamic-umalqura`, `ethiopic`, or `chinese`: every
+calendar Date Picker and Date Input draw.
+
+Absent is the locale's own where its months are the Gregorian months,
+such as `buddhist` for `th-TH`, and `gregory` for every other, such as
+`persian` for `fa-IR`, so a date written here reads as the same date a
+Date Picker beside it shows. Write `calendar="persian"` for Mehr 14, 1405. */
   "prop:calendar"?: (HelixFormatDate["calendar"]) | undefined;
   /** The timestamp, in any format `Date` can parse.
 
@@ -16100,6 +16259,14 @@ browser may use either. */
   "prop:dateStyle"?: (HelixFormatDate["dateStyle"]) | undefined;
   /** How the day of the month is written, where a date is shown. */
   "prop:day"?: (HelixFormatDate["day"]) | undefined;
+  /** Writes the part of the day in words, such as "in the morning" or "at
+night", in its `long`, `short`, or `narrow` form, where `hour` is on a
+twelve-hour clock. */
+  "attr:day-period"?: (HelixFormatDate["dayPeriod"]) | undefined;
+  /** Writes the part of the day in words, such as "in the morning" or "at
+night", in its `long`, `short`, or `narrow` form, where `hour` is on a
+twelve-hour clock. */
+  "prop:dayPeriod"?: (HelixFormatDate["dayPeriod"]) | undefined;
   /** Shows how long ago the timestamp was, in a compact form such as "3h", in
 place of the date.
 
@@ -16117,6 +16284,12 @@ Off by default, which draws the date as one run of text, as Shoelace and
 Web Awesome do. An `elapsed` or `relative` reading is one phrase either
 way. */
   "prop:fields"?: (HelixFormatDate["fields"]) | undefined;
+  /** How many digits of a fraction of a second to write after `second`: 1, 2,
+or 3, as in 09:41:07.250. */
+  "attr:fractional-second-digits"?: (HelixFormatDate["fractionalSecondDigits"]) | undefined;
+  /** How many digits of a fraction of a second to write after `second`: 1, 2,
+or 3, as in 09:41:07.250. */
+  "prop:fractionalSecondDigits"?: (HelixFormatDate["fractionalSecondDigits"]) | undefined;
   /** Draws an `elapsed` or `relative` reading once and leaves it, where it
 would otherwise move on as it goes stale.
 
@@ -16179,9 +16352,13 @@ Empty is the runtime's own. */
 
 Empty is the runtime's own. */
   "prop:timeZone"?: (HelixFormatDate["timeZone"]) | undefined;
-  /** Shows the name of the time zone, in its `long` or `short` form. */
+  /** Shows the name of the time zone: `long` or `short`, as Pacific Daylight
+Time or PDT, `longOffset` or `shortOffset`, as GMT-07:00 or GMT-7, or
+`longGeneric` or `shortGeneric`, as Pacific Time or PT. */
   "attr:time-zone-name"?: (HelixFormatDate["timeZoneName"]) | undefined;
-  /** Shows the name of the time zone, in its `long` or `short` form. */
+  /** Shows the name of the time zone: `long` or `short`, as Pacific Daylight
+Time or PDT, `longOffset` or `shortOffset`, as GMT-07:00 or GMT-7, or
+`longGeneric` or `shortGeneric`, as Pacific Time or PT. */
   "prop:timeZoneName"?: (HelixFormatDate["timeZoneName"]) | undefined;
   /** How the weekday is written, where one is shown. */
   "prop:weekday"?: (HelixFormatDate["weekday"]) | undefined;
@@ -30436,6 +30613,14 @@ rather than a thumb sitting on nothing. */
 middle of the track, or `end` at `max`. Absent is `start`. A range fills
 between its thumbs and ignores it. */
   origin?: (HelixSlider["origin"]) | undefined;
+  /** How far Page Up and Page Down move a thumb, in the slider's own units, as
+React Aria's `pageSize` and Zag's `largeStep` do. Absent leaves the keys
+to the platform, which moves a tenth of the track. */
+  "page-step"?: (HelixSlider["pageStep"] | `${number}`) | undefined;
+  /** How far Page Up and Page Down move a thumb, in the slider's own units, as
+React Aria's `pageSize` and Zag's `largeStep` do. Absent leaves the keys
+to the platform, which moves a tenth of the track. */
+  pageStep?: (HelixSlider["pageStep"]) | undefined;
   /** Adds a second thumb, so the value is a pair.
 
 The pair is one string, `"10,50"`, which is what `value` and
@@ -30690,6 +30875,14 @@ rather than a thumb sitting on nothing. */
 middle of the track, or `end` at `max`. Absent is `start`. A range fills
 between its thumbs and ignores it. */
   "prop:origin"?: (HelixSlider["origin"]) | undefined;
+  /** How far Page Up and Page Down move a thumb, in the slider's own units, as
+React Aria's `pageSize` and Zag's `largeStep` do. Absent leaves the keys
+to the platform, which moves a tenth of the track. */
+  "attr:page-step"?: (HelixSlider["pageStep"] | `${number}`) | undefined;
+  /** How far Page Up and Page Down move a thumb, in the slider's own units, as
+React Aria's `pageSize` and Zag's `largeStep` do. Absent leaves the keys
+to the platform, which moves a tenth of the track. */
+  "prop:pageStep"?: (HelixSlider["pageStep"]) | undefined;
   /** Adds a second thumb, so the value is a pair.
 
 The pair is one string, `"10,50"`, which is what `value` and
@@ -34612,6 +34805,9 @@ export type HelixTimeInputHelixBeforeCloseElementEvent =
 /** `helix-before-open` event type */
 export type HelixTimeInputHelixBeforeOpenElementEvent =
   HelixTimeInputElementEvent<HelixBeforeOpenEvent>;
+/** `helix-clear` event type */
+export type HelixTimeInputHelixClearElementEvent =
+  HelixTimeInputElementEvent<HelixClearEvent>;
 
 export type HelixTimeInputProps = {
   /** What a row of segments reports when the field is required and every
@@ -34636,6 +34832,18 @@ are not, where `bad-input-message` is not set. `{kind}` is `date` or
 are not, where `bad-input-message` is not set. `{kind}` is `date` or
 `time`. */
   incompleteMessage?: (HelixTimeInput["incompleteMessage"]) | undefined;
+  /** What a screen reader hears before the segments of a range's second date
+or time, after each segment's own name. */
+  "range-end-label"?: (HelixTimeInput["rangeEndLabel"]) | undefined;
+  /** What a screen reader hears before the segments of a range's second date
+or time, after each segment's own name. */
+  rangeEndLabel?: (HelixTimeInput["rangeEndLabel"]) | undefined;
+  /** What a screen reader hears before the segments of a range's first date
+or time, after each segment's own name: "month, Start, Stay". */
+  "range-start-label"?: (HelixTimeInput["rangeStartLabel"]) | undefined;
+  /** What a screen reader hears before the segments of a range's first date
+or time, after each segment's own name: "month, Start, Stay". */
+  rangeStartLabel?: (HelixTimeInput["rangeStartLabel"]) | undefined;
   /** Whether the field is a row of segments, one for each part of the date or
 time, in place of a line of text.
 
@@ -34805,6 +35013,14 @@ the field and does not reach that one. */
 Empty leaves the attribute off, which is the browser's default and is what
 lets autofill work at all. */
   autocomplete?: (HelixTimeInput["autocomplete"]) | undefined;
+  /** Whether the field shows a button that empties it, as Input's `clearable`
+does. Shown only while the field holds something to clear and is neither
+disabled nor read-only. */
+  clearable?: (HelixTimeInput["clearable"]) | undefined;
+  /** The accessible name of the clear button, which shows only an icon. */
+  "clear-label"?: (HelixTimeInput["clearLabel"]) | undefined;
+  /** The accessible name of the clear button, which shows only an icon. */
+  clearLabel?: (HelixTimeInput["clearLabel"]) | undefined;
   /** Times that cannot be chosen, as `HH:mm`, separated by commas or spaces.
 
 Handed to the list, which offers them as unavailable, and checked against
@@ -34908,6 +35124,12 @@ never something this element would refuse to read back. */
   "unavailable-message"?: (HelixTimeInput["unavailableMessage"]) | undefined;
   /** The message shown when `disable-times` bars a time. */
   unavailableMessage?: (HelixTimeInput["unavailableMessage"]) | undefined;
+  /** The message for text that is no time, where `bad-input-message` is not
+set. `{mode}` is `single`, `range`, or `multiple`, and `{shape}` is `HH:mm`, or `HH:mm:ss` with `seconds`. */
+  "unreadable-message"?: (HelixTimeInput["unreadableMessage"]) | undefined;
+  /** The message for text that is no time, where `bad-input-message` is not
+set. `{mode}` is `single`, `range`, or `multiple`, and `{shape}` is `HH:mm`, or `HH:mm:ss` with `seconds`. */
+  unreadableMessage?: (HelixTimeInput["unreadableMessage"]) | undefined;
   /** Whether the panel shows one list of times or a column for each part of the
 time.
 
@@ -34977,6 +35199,8 @@ a consumer handing over `new Date()` gets the time of day they expected. */
   "onhelix-before-open"?: ((
     e: HelixTimeInputHelixBeforeOpenElementEvent,
   ) => void) | undefined;
+  /** Fired after the clear button has emptied the field, after `input` and `change`. */
+  "onhelix-clear"?: ((e: HelixTimeInputHelixClearElementEvent) => void) | undefined;
   /** Fired after the value changes. */
   oninput?: ((e: HelixTimeInputElementEvent) => void) | undefined;
 };
@@ -35004,6 +35228,18 @@ are not, where `bad-input-message` is not set. `{kind}` is `date` or
 are not, where `bad-input-message` is not set. `{kind}` is `date` or
 `time`. */
   "prop:incompleteMessage"?: (HelixTimeInput["incompleteMessage"]) | undefined;
+  /** What a screen reader hears before the segments of a range's second date
+or time, after each segment's own name. */
+  "attr:range-end-label"?: (HelixTimeInput["rangeEndLabel"]) | undefined;
+  /** What a screen reader hears before the segments of a range's second date
+or time, after each segment's own name. */
+  "prop:rangeEndLabel"?: (HelixTimeInput["rangeEndLabel"]) | undefined;
+  /** What a screen reader hears before the segments of a range's first date
+or time, after each segment's own name: "month, Start, Stay". */
+  "attr:range-start-label"?: (HelixTimeInput["rangeStartLabel"]) | undefined;
+  /** What a screen reader hears before the segments of a range's first date
+or time, after each segment's own name: "month, Start, Stay". */
+  "prop:rangeStartLabel"?: (HelixTimeInput["rangeStartLabel"]) | undefined;
   /** Whether the field is a row of segments, one for each part of the date or
 time, in place of a line of text.
 
@@ -35173,6 +35409,14 @@ the field and does not reach that one. */
 Empty leaves the attribute off, which is the browser's default and is what
 lets autofill work at all. */
   "prop:autocomplete"?: (HelixTimeInput["autocomplete"]) | undefined;
+  /** Whether the field shows a button that empties it, as Input's `clearable`
+does. Shown only while the field holds something to clear and is neither
+disabled nor read-only. */
+  "prop:clearable"?: (HelixTimeInput["clearable"]) | undefined;
+  /** The accessible name of the clear button, which shows only an icon. */
+  "attr:clear-label"?: (HelixTimeInput["clearLabel"]) | undefined;
+  /** The accessible name of the clear button, which shows only an icon. */
+  "prop:clearLabel"?: (HelixTimeInput["clearLabel"]) | undefined;
   /** Times that cannot be chosen, as `HH:mm`, separated by commas or spaces.
 
 Handed to the list, which offers them as unavailable, and checked against
@@ -35276,6 +35520,12 @@ never something this element would refuse to read back. */
   "attr:unavailable-message"?: (HelixTimeInput["unavailableMessage"]) | undefined;
   /** The message shown when `disable-times` bars a time. */
   "prop:unavailableMessage"?: (HelixTimeInput["unavailableMessage"]) | undefined;
+  /** The message for text that is no time, where `bad-input-message` is not
+set. `{mode}` is `single`, `range`, or `multiple`, and `{shape}` is `HH:mm`, or `HH:mm:ss` with `seconds`. */
+  "attr:unreadable-message"?: (HelixTimeInput["unreadableMessage"]) | undefined;
+  /** The message for text that is no time, where `bad-input-message` is not
+set. `{mode}` is `single`, `range`, or `multiple`, and `{shape}` is `HH:mm`, or `HH:mm:ss` with `seconds`. */
+  "prop:unreadableMessage"?: (HelixTimeInput["unreadableMessage"]) | undefined;
   /** Whether the panel shows one list of times or a column for each part of the
 time.
 
@@ -35344,6 +35594,8 @@ a consumer handing over `new Date()` gets the time of day they expected. */
   "on:helix-before-open"?: ((
     e: HelixTimeInputHelixBeforeOpenElementEvent,
   ) => void) | undefined;
+  /** Fired after the clear button has emptied the field, after `input` and `change`. */
+  "on:helix-clear"?: ((e: HelixTimeInputHelixClearElementEvent) => void) | undefined;
   /** Fired after the value changes. */
   "on:input"?: ((e: HelixTimeInputElementEvent) => void) | undefined;
 
@@ -36439,6 +36691,18 @@ and this one was the English a form in another language still spoke in
 the bubble it raises on submit: `feedback` replaces the message under
 the field and does not reach that one. */
   valueMissingMessage?: (HelixToggleGroup["valueMissingMessage"]) | undefined;
+  /** Whether a press on the chosen item, or Space or Enter on it, takes it
+back so nothing is chosen, as React Aria's `ToggleButtonGroup` and
+Radix's `ToggleGroup` do in a single group. Absent, a single group always
+keeps its choice once it has one, as a radio group does. A multiple group
+releases a pressed item either way. */
+  "allow-empty-selection"?: (HelixToggleGroup["allowEmptySelection"]) | undefined;
+  /** Whether a press on the chosen item, or Space or Enter on it, takes it
+back so nothing is chosen, as React Aria's `ToggleButtonGroup` and
+Radix's `ToggleGroup` do in a single group. Absent, a single group always
+keeps its choice once it has one, as a radio group does. A multiple group
+releases a pressed item either way. */
+  allowEmptySelection?: (HelixToggleGroup["allowEmptySelection"]) | undefined;
   /** Where the group's label sits. `start` puts it on the track's line.
 
 Absent is above, which is what a field looks like and what almost every
@@ -36630,6 +36894,18 @@ and this one was the English a form in another language still spoke in
 the bubble it raises on submit: `feedback` replaces the message under
 the field and does not reach that one. */
   "prop:valueMissingMessage"?: (HelixToggleGroup["valueMissingMessage"]) | undefined;
+  /** Whether a press on the chosen item, or Space or Enter on it, takes it
+back so nothing is chosen, as React Aria's `ToggleButtonGroup` and
+Radix's `ToggleGroup` do in a single group. Absent, a single group always
+keeps its choice once it has one, as a radio group does. A multiple group
+releases a pressed item either way. */
+  "bool:allow-empty-selection"?: (HelixToggleGroup["allowEmptySelection"]) | undefined;
+  /** Whether a press on the chosen item, or Space or Enter on it, takes it
+back so nothing is chosen, as React Aria's `ToggleButtonGroup` and
+Radix's `ToggleGroup` do in a single group. Absent, a single group always
+keeps its choice once it has one, as a radio group does. A multiple group
+releases a pressed item either way. */
+  "prop:allowEmptySelection"?: (HelixToggleGroup["allowEmptySelection"]) | undefined;
   /** Where the group's label sits. `start` puts it on the track's line.
 
 Absent is above, which is what a field looks like and what almost every
@@ -45722,6 +45998,12 @@ export type CustomElements = {
    *
    * Methods that can be called to access component functionality.
    *
+   * - `formResetCallback() => void`: Returns the control to its `defaultValue`, or to its `value` attribute
+   * where there is no `default-value`.
+   *
+   * Both halves are dropped, the consumer's and the control's, because a
+   * reset means the form is as it was served. Clearing only the internal one
+   * would leave a control that had been written to stuck at that value.
    * - `requestValue(next: string) => boolean`: Requests a new value, and returns whether the change was applied.
    *
    * Announces before it acts, so `preventDefault()` on the `helix-before-change` is
@@ -45729,12 +46011,6 @@ export type CustomElements = {
    * itself, whether or not a consumer declared `value`: a declared property
    * is a seed and a correction, the way `<input value>` is, and a consumer
    * who wants the change for themselves refuses it and assigns their own.
-   * - `formResetCallback() => void`: Returns the control to its `defaultValue`, or to its `value` attribute
-   * where there is no `default-value`.
-   *
-   * Both halves are dropped, the consumer's and the control's, because a
-   * reset means the form is as it was served. Clearing only the internal one
-   * would leave a control that had been written to stuck at that value.
    * - `formStateRestoreCallback(state: string | File | FormData | null) => void`: Restores the value when the browser brings a form back.
    *
    * Falling back to what the markup declared rather than to empty, because
@@ -47144,6 +47420,10 @@ export type CustomElements = {
    * - `incomplete-message`/`incompleteMessage`: What a row of segments reports while some segments are set and others
    * are not, where `bad-input-message` is not set. `{kind}` is `date` or
    * `time`.
+   * - `range-end-label`/`rangeEndLabel`: What a screen reader hears before the segments of a range's second date
+   * or time, after each segment's own name.
+   * - `range-start-label`/`rangeStartLabel`: What a screen reader hears before the segments of a range's first date
+   * or time, after each segment's own name: "month, Start, Stay".
    * - `segmented`: Whether the field is a row of segments, one for each part of the date or
    * time, in place of a line of text.
    *
@@ -47228,27 +47508,39 @@ export type CustomElements = {
    * and this one was the English a form in another language still spoke in
    * the bubble it raises on submit: `feedback` replaces the message under
    * the field and does not reach that one.
-   * - `autocomplete`: What the browser may autofill here, as one of the platform's own tokens.
+   * - `autocomplete`: What the browser may autofill here, as one of the platform's own tokens,
+   * such as `bday`.
    *
    * Empty leaves the attribute off, which is the browser's default and is what
    * lets autofill work at all: hardcoding `off` here means a birthday or a
-   * postal code can never be filled in for a reader.
-   * - `calendar`: The calendar the written date and the calendar's days are in: `gregory`,
-   * `buddhist`, `japanese`, `roc`, or `iso8601`.
-   *
-   * Absent is the locale's own where it is one of the five, and `gregory` for
-   * every other, as Date Picker's `calendar` is. The value is `YYYY-MM-DD` in
-   * every calendar, and a focused field is ISO in every calendar. In
-   * `segmented`, the segments are the Gregorian day, month, and year, in the
-   * order the locale writes them, or ISO order for `iso8601`.
+   * postal code can never be filled in for a reader. With `segmented`, a
+   * hidden native date input carries it, since no browser fills the segments.
+   * - `calendar`: The calendar the written date, the segments, and the calendar's days are
+   * in: `gregory`, `buddhist`, `japanese`, `roc`, or `iso8601`, or a calendar
+   * with months of its own that Date Picker's `calendar` names, such as
+   * `persian`, `hebrew`, `islamic-umalqura`, `ethiopic`, or `chinese`.
+   *
+   * Absent is the locale's own where its months are the Gregorian months, and
+   * `gregory` for every other, as Date Picker's `calendar` is. The value is
+   * `YYYY-MM-DD` in every calendar, and a focused text field is ISO in every
+   * calendar. In `segmented`, the segments are the day, month, and year as
+   * the calendar counts them, in the order the locale writes them: Mehr 14,
+   * 1405 is month 7 and day 14 of 1405 under `persian`. Under the five with
+   * Gregorian months they are the Gregorian day, month, and year, or ISO order
+   * for `iso8601`.
    * - `calendar-label`/`calendarLabel`: The name of the calendar's grid of days, read by screen readers.
+   * - `clearable`: Whether the field shows a button that empties it, as Input's `clearable`
+   * does. Shown only while the field holds something to clear and is neither
+   * disabled nor read-only.
+   * - `clear-label`/`clearLabel`: The accessible name of the clear button, which shows only an icon.
    * - `date-style`/`dateStyle`: How a date is written in the field: `short` through `full`, or ISO.
    *
    * **The field renders when it is idle and holds the value when it is being
    * edited.** A written date is a rendering, and a document being edited must
    * not be a rendering of something else: `Intl.DateTimeFormat` formats and does
-   * not parse, so `4 August 2026` cannot be typed back, and writing a parser per
-   * locale is how a field ends up rejecting what it just displayed.
+   * not parse, so a rendering such as `Tuesday, August 4, 2026` is no text to
+   * edit. The field does read a date typed in the locale's order and digits as
+   * you leave it, which covers what a reader types.
    *
    * The way out is not to choose between the two but to separate them in time.
    * Idle, the field shows `4 August 2026`, which is what a date is for reading.
@@ -47316,6 +47608,9 @@ export type CustomElements = {
    *
    * **The name goes in**, so a row of them is heard as which one each
    * removes rather than as "Remove" said once per date.
+   * - `selection-label`/`selectionLabel`: What a screen reader hears about the dates chosen in the calendar, with
+   * `{kind}`, `{start}`, `{end}` and `{count}` filled in as Date Picker's
+   * `selection-label` says.
    * - `step`: How far apart the selectable dates are, in days.
    *
    * `<input type="date" step>`'s own unit, handed to the calendar this renders
@@ -47323,8 +47618,13 @@ export type CustomElements = {
    * where there is one and from 1 January 1970 where there is not, which is the
    * platform's base.
    * - `step-mismatch-message`/`stepMismatchMessage`: The message shown when a date is not on `step`.
+   * - `time-zone`/`timeZone`: The time zone today is read in, such as `America/New_York`, handed to the
+   * calendar: the day marked today, and the month an empty field opens on.
+   * Empty is the reader's own. Dates are plain `YYYY-MM-DD` and carry no zone.
    * - `trigger-label`/`triggerLabel`: The name of the button that opens the calendar, read by screen readers.
    * - `unavailable-message`/`unavailableMessage`: The message shown when `disable-dates` or `disable-days` bars a date.
+   * - `unreadable-message`/`unreadableMessage`: The message for text that is no date, where `bad-input-message` is not
+   * set. `{mode}` is `single`, `range`, or `multiple`.
    * - `year-view-label`/`yearViewLabel`: The name of the calendar's heading where it shows a page of years, with
    * `{heading}` filled in.
    * - `disabled`: Whether the control is disabled and cannot be used.
@@ -47404,12 +47704,14 @@ export type CustomElements = {
    * - `helix-before-change`: Fired before the date changes. Cancelable: call `preventDefault()` to keep the current date.
    * - `helix-before-close`: Fired before the calendar closes. Cancelable: call `preventDefault()` to keep it open.
    * - `helix-before-open`: Fired before the calendar opens. Cancelable: call `preventDefault()` to keep it closed.
+   * - `helix-clear`: Fired after the clear button has emptied the field, after `input` and `change`.
    * - `input`: Fired after the value changes.
    *
    * ## Slots
    *
    * Areas where markup can be added to the component.
    *
+   * - `clear-icon`: Replaces the cross on the clear button, under `clearable`.
    * - `end`: Content after the date, before the trigger, such as a clear button.
    * - `feedback`: The error message under the field.
    * - `hint`: The help text under the field.
@@ -47498,6 +47800,7 @@ export type CustomElements = {
    *
    * Custom selectors for styling elements within the component.
    *
+   * - `clear`: The button that empties the field, under `clearable`, while it holds a date.
    * - `control`: The text input.
    * - `date`: One held date, as a tag, in `multiple`.
    * - `date-cell`: The tag's grid cell, which a tag draws only inside a tag group.
@@ -47539,8 +47842,10 @@ export type CustomElements = {
    * - `picker-periods`: The grid of months or years.
    * - `picker-previous`: The control that moves to the previous month.
    * - `picker-previous-mark`: The icon on the previous month control.
+   * - `picker-selection`: The chosen date or range in words, which screen readers hear when it changes. Drawn for screen readers only.
    * - `picker-week`: One row of days.
    * - `picker-weekday`: A column header naming a day of the week.
+   * - `range-separator`: The dash between a range's two rows of segments, in `segmented`, beside `literal`.
    * - `rest`: The count of dates beyond the ones shown. It is a `<button>` with `expandable` and a `<span>` without it.
    * - `segment`: One part of the date, a year, a month or a day, in `segmented`.
    * - `segment-placeholder`: A segment with nothing in it yet. Applied with `segment`.
@@ -47554,6 +47859,7 @@ export type CustomElements = {
    *
    * These can be used to apply styling when a component is in a given state.
    *
+   * - `blank`: The field holds no date.
    * - `invalid`: The field has an error to show, from the browser's validation or from your `feedback`.
    * - `open`: The calendar is open.
    * - `settled`: Set one frame after the first render. Transitions wait for it, so an element does not animate its own arrival.
@@ -47615,14 +47921,16 @@ export type CustomElements = {
    * `ja-JP-u-ca-japanese`, and `gregory` for every other, such as `persian`
    * for `fa-IR`.
    *
-   * `persian`, `hebrew`, `islamic-umalqura`, `islamic-civil`, `ethiopic`,
-   * `coptic`, and `indian` draw a calendar with months of its own, as React
-   * Aria's calendars do: each grid is one of that calendar's months, the
-   * Hebrew leap month and Ethiopia's five-day thirteenth month included, and
-   * Previous, Next and the page keys move by those months. `month` and
+   * `persian`, `hebrew`, `islamic`, `islamic-umalqura`, `islamic-civil`,
+   * `islamic-tbla`, `islamic-rgsa`, `ethiopic`, `ethioaa`, `coptic`,
+   * `indian`, `chinese`, and `dangi` draw a calendar with months of its own,
+   * as React Aria's calendars do: each grid is one of that calendar's months,
+   * the Hebrew and Chinese leap months and Ethiopia's five-day thirteenth
+   * month included, and Previous, Next and the page keys move by those
+   * months. With `max-view`, the months view shows that calendar's year, of
+   * twelve or thirteen months, and the years view its years. `month` and
    * `helix-navigate` then name a month by its first day, `YYYY-MM-DD`. The
-   * heading stays text, as the months and years views are drawn in Gregorian
-   * months only. The value is `YYYY-MM-DD` in every calendar.
+   * value is `YYYY-MM-DD` in every calendar.
    * - `default-month`/`defaultMonth`: The month to open on when `month` is not set.
    * - `disable-dates`/`disableDates`: Dates that cannot be chosen, as `YYYY-MM-DD`, separated by commas or
    * spaces.
@@ -47685,6 +47993,11 @@ export type CustomElements = {
    * value and stays reachable, which is what a form showing a value somebody
    * else set needs.
    * - `required`: Stops the form from submitting while no date is chosen.
+   * - `selection-label`/`selectionLabel`: What a screen reader hears about the chosen dates: the grid's
+   * description, said again whenever the dates change. `{kind}` is `date`,
+   * `start` while a range holds one end, `range`, or `dates` for `multiple`.
+   * `{start}` and `{end}` are dates written in `locale`, and `{count}` is how
+   * many dates are chosen.
    * - `step`: How far apart the selectable dates are, in days.
    *
    * `<input type="date" step>`'s own unit, counted from `min` where there is
@@ -47813,6 +48126,12 @@ export type CustomElements = {
    *
    * Methods that can be called to access component functionality.
    *
+   * - `formResetCallback() => void`: Returns the control to its `defaultValue`, or to its `value` attribute
+   * where there is no `default-value`.
+   *
+   * Both halves are dropped, the consumer's and the control's, because a
+   * reset means the form is as it was served. Clearing only the internal one
+   * would leave a control that had been written to stuck at that value.
    * - `requestValue(next: string) => boolean`: Requests a new value, and returns whether the change was applied.
    *
    * Announces before it acts, so `preventDefault()` on the `helix-before-change` is
@@ -47820,18 +48139,19 @@ export type CustomElements = {
    * itself, whether or not a consumer declared `value`: a declared property
    * is a seed and a correction, the way `<input value>` is, and a consumer
    * who wants the change for themselves refuses it and assigns their own.
-   * - `formResetCallback() => void`: Returns the control to its `defaultValue`, or to its `value` attribute
-   * where there is no `default-value`.
-   *
-   * Both halves are dropped, the consumer's and the control's, because a
-   * reset means the form is as it was served. Clearing only the internal one
-   * would leave a control that had been written to stuck at that value.
    * - `formStateRestoreCallback(state: string | File | FormData | null) => void`: Restores the value when the browser brings a form back.
    *
    * Falling back to what the markup declared rather than to empty, because
    * a restore with no state is a form the browser has nothing recorded for,
    * which is the same situation as a fresh one.
    * - `focus(options?: FocusOptions) => void`: Moves focus to the control, as focusing a native control does.
+   * - `showChosen() => void`: Shows the days again, on the month of the chosen date, with the tab stop
+   * on that date, forgetting the month and the day the reader browsed to.
+   *
+   * Date Input calls it each time its panel opens, which is where the APG
+   * date picker dialog puts focus. Measured before this: from August 4, two
+   * presses of Page Down, Escape, and Down again opened on October 4.
+   * A `month` you set stays until the reader pages away from it.
    * - `formDisabledCallback(disabled: boolean) => void`: Called by the browser when an ancestor fieldset is disabled or enabled.
    *
    * **The argument is the effective state, and taking it whole is what latched
@@ -47881,6 +48201,7 @@ export type CustomElements = {
    * - `--date-picker-feedback-color`: The color of the message under the calendar, while `feedback` is set.
    * - `--date-picker-period-size`: Height of a month or a year in the months and years views, where `max-view` is set.
    * - `--date-picker-range-color`: Band behind the days in a range.
+   * - `--date-picker-range-preview-color`: Band behind the days a waiting range is drawn to, before its second end is chosen.
    * - `--date-picker-row-size`: Height of a week row.
    * - `--date-picker-selected-color`: Fill behind a selected day.
    * - `--date-picker-track-size`: Width of a column, which is what sets the space between days.
@@ -47891,7 +48212,7 @@ export type CustomElements = {
    * Custom selectors for styling elements within the component.
    *
    * - `cell`: One column of a week row. A range is painted on the cells.
-   * - `cell-range-end`: The cell of a range's last day, beside `cell`.
+   * - `cell-range-end`: The cell of a range's last day, beside `cell`, or of the day a waiting range is drawn to.
    * - `cell-range-middle`: A cell between a range's ends, beside `cell`.
    * - `cell-range-start`: The cell of a range's first day, beside `cell`.
    * - `day`: The shape inside a cell. A single chosen date is painted on it.
@@ -47917,6 +48238,7 @@ export type CustomElements = {
    * - `periods`: The grid of months or years.
    * - `previous`: The control that moves to the previous month.
    * - `previous-mark`: The glyph on the previous month control, where none is slotted.
+   * - `selection`: The chosen date or range in words, which screen readers hear when it changes. Drawn for screen readers only.
    * - `week`: One row of days.
    * - `weekday`: A column header naming a day of the week. It shows the short name and says the full one.
    *
@@ -47924,7 +48246,11 @@ export type CustomElements = {
    *
    * These can be used to apply styling when a component is in a given state.
    *
-   * - `invalid`: While `invalid` is set or `feedback` says what is wrong.
+   * - `blank`: While no date is chosen.
+   * - `invalid`: While `invalid` is set, `feedback` says what is wrong, the picker holds a date outside `min` and `max` or one it bars, or it is `required`, holds no date, and the reader has answered once or a form has refused it.
+   * - `month-view`: While the months of a year are shown, where `max-view` is set.
+   * - `range-pending`: While a `range` holds its first end and waits for the second.
+   * - `year-view`: While a page of years is shown, where `max-view` is `year`.
    * - `settled`: Set one frame after the first render. Transitions wait for it, so an element does not animate its own arrival.
    */
   "helix-date-picker": Partial<
@@ -50475,12 +50801,14 @@ export type CustomElements = {
    * Component attributes and properties that can be applied to the element or by using JavaScript.
    *
    * - `calendar`: The calendar a date is written in: `gregory`, `buddhist`, `japanese`,
-   * `roc`, or `iso8601`, the calendars Date Picker and Date Input draw.
-   *
-   * Absent is the locale's own where it is one of the five, such as
-   * `buddhist` for `th-TH`, and `gregory` for every other, such as `persian`
-   * for `fa-IR`, so a date written here reads as the same date a Date Picker
-   * beside it shows.
+   * `roc`, or `iso8601`, or a calendar with months of its own, such as
+   * `persian`, `hebrew`, `islamic-umalqura`, `ethiopic`, or `chinese`: every
+   * calendar Date Picker and Date Input draw.
+   *
+   * Absent is the locale's own where its months are the Gregorian months,
+   * such as `buddhist` for `th-TH`, and `gregory` for every other, such as
+   * `persian` for `fa-IR`, so a date written here reads as the same date a
+   * Date Picker beside it shows. Write `calendar="persian"` for Mehr 14, 1405.
    * - `date`: The timestamp, in any format `Date` can parse.
    *
    * An ISO string is what an API sends and what `<time datetime>` takes, so it
@@ -50499,6 +50827,9 @@ export type CustomElements = {
    * - `date-style`/`dateStyle`: The locale's own pattern for the date: `full`, `long`, `medium`, or
    * `short`. Set, it stands in for `weekday`, `day`, `month`, `year` and `era`.
    * - `day`: How the day of the month is written, where a date is shown.
+   * - `day-period`/`dayPeriod`: Writes the part of the day in words, such as "in the morning" or "at
+   * night", in its `long`, `short`, or `narrow` form, where `hour` is on a
+   * twelve-hour clock.
    * - `elapsed`: Shows how long ago the timestamp was, in a compact form such as "3h", in
    * place of the date.
    *
@@ -50513,6 +50844,8 @@ export type CustomElements = {
    * Off by default, which draws the date as one run of text, as Shoelace and
    * Web Awesome do. An `elapsed` or `relative` reading is one phrase either
    * way.
+   * - `fractional-second-digits`/`fractionalSecondDigits`: How many digits of a fraction of a second to write after `second`: 1, 2,
+   * or 3, as in 09:41:07.250.
    * - `frozen`: Draws an `elapsed` or `relative` reading once and leaves it, where it
    * would otherwise move on as it goes stale.
    *
@@ -50550,7 +50883,9 @@ export type CustomElements = {
    * - `time-zone`/`timeZone`: The time zone to read the timestamp in.
    *
    * Empty is the runtime's own.
-   * - `time-zone-name`/`timeZoneName`: Shows the name of the time zone, in its `long` or `short` form.
+   * - `time-zone-name`/`timeZoneName`: Shows the name of the time zone: `long` or `short`, as Pacific Daylight
+   * Time or PDT, `longOffset` or `shortOffset`, as GMT-07:00 or GMT-7, or
+   * `longGeneric` or `shortGeneric`, as Pacific Time or PT.
    * - `weekday`: How the weekday is written, where one is shown.
    * - `year`: How the year is written, where a date is shown.
    * - `whenSettled`: Resolves a frame after the first update, when transitions are switched on.
@@ -50581,6 +50916,7 @@ export type CustomElements = {
    * - `day`: The day of the month, with `fields`.
    * - `day-period`: AM or PM, or the locale's word for the part of the day, with `fields`.
    * - `era`: The era, such as AD, with `fields` and `era`.
+   * - `fractional-second`: The fraction of a second, with `fields` and `fractional-second-digits`.
    * - `hour`: The hour, with `fields`.
    * - `minute`: The minute, with `fields`.
    * - `month`: The month, with `fields`.
@@ -56279,6 +56615,7 @@ export type CustomElements = {
    * - `time-day`: Format Date's `day`, forwarded for a time drawn as fields. An elapsed time draws none.
    * - `time-day-period`: Format Date's `day-period`, forwarded for a time drawn as fields. An elapsed time draws none.
    * - `time-era`: Format Date's `era`, forwarded for a time drawn as fields. An elapsed time draws none.
+   * - `time-fractional-second`: Format Date's `fractional-second`, forwarded for a time drawn as fields. An elapsed time draws none.
    * - `time-hour`: Format Date's `hour`, forwarded for a time drawn as fields. An elapsed time draws none.
    * - `time-minute`: Format Date's `minute`, forwarded for a time drawn as fields. An elapsed time draws none.
    * - `time-month`: Format Date's `month`, forwarded for a time drawn as fields. An elapsed time draws none.
@@ -61359,6 +61696,9 @@ export type CustomElements = {
    * - `origin`: Where a single thumb's fill starts: `start` at `min`, `center` at the
    * middle of the track, or `end` at `max`. Absent is `start`. A range fills
    * between its thumbs and ignores it.
+   * - `page-step`/`pageStep`: How far Page Up and Page Down move a thumb, in the slider's own units, as
+   * React Aria's `pageSize` and Zag's `largeStep` do. Absent leaves the keys
+   * to the platform, which moves a tenth of the track.
    * - `range`: Adds a second thumb, so the value is a pair.
    *
    * The pair is one string, `"10,50"`, which is what `value` and
@@ -61566,6 +61906,8 @@ export type CustomElements = {
    *
    * These can be used to apply styling when a component is in a given state.
    *
+   * - `dragging`: A thumb is being dragged, by its thumb or from a press on the track.
+   * - `focus-visible`: A thumb has focus that the keyboard brought, where the browser draws a focus ring.
    * - `invalid`: The slider has an error to show, from the browser's validation or from your `feedback`.
    * - `settled`: Set one frame after the first render. Transitions wait for it, so an element does not animate its own arrival.
    */
@@ -64629,6 +64971,10 @@ export type CustomElements = {
    * - `incomplete-message`/`incompleteMessage`: What a row of segments reports while some segments are set and others
    * are not, where `bad-input-message` is not set. `{kind}` is `date` or
    * `time`.
+   * - `range-end-label`/`rangeEndLabel`: What a screen reader hears before the segments of a range's second date
+   * or time, after each segment's own name.
+   * - `range-start-label`/`rangeStartLabel`: What a screen reader hears before the segments of a range's first date
+   * or time, after each segment's own name: "month, Start, Stay".
    * - `segmented`: Whether the field is a row of segments, one for each part of the date or
    * time, in place of a line of text.
    *
@@ -64717,6 +65063,10 @@ export type CustomElements = {
    *
    * Empty leaves the attribute off, which is the browser's default and is what
    * lets autofill work at all.
+   * - `clearable`: Whether the field shows a button that empties it, as Input's `clearable`
+   * does. Shown only while the field holds something to clear and is neither
+   * disabled nor read-only.
+   * - `clear-label`/`clearLabel`: The accessible name of the clear button, which shows only an icon.
    * - `disable-times`/`disableTimes`: Times that cannot be chosen, as `HH:mm`, separated by commas or spaces.
    *
    * Handed to the list, which offers them as unavailable, and checked against
@@ -64765,6 +65115,8 @@ export type CustomElements = {
    * never something this element would refuse to read back.
    * - `trigger-label`/`triggerLabel`: The name of the button that opens the list, read by screen readers.
    * - `unavailable-message`/`unavailableMessage`: The message shown when `disable-times` bars a time.
+   * - `unreadable-message`/`unreadableMessage`: The message for text that is no time, where `bad-input-message` is not
+   * set. `{mode}` is `single`, `range`, or `multiple`, and `{shape}` is `HH:mm`, or `HH:mm:ss` with `seconds`.
    * - `variant`: Whether the panel shows one list of times or a column for each part of the
    * time.
    *
@@ -64847,12 +65199,14 @@ export type CustomElements = {
    * - `helix-before-change`: Fired before the time changes. Cancelable: canceling it stops the change and leaves the decision to you.
    * - `helix-before-close`: Fired before the list closes. Cancelable: canceling it keeps the list open and leaves the decision to you.
    * - `helix-before-open`: Fired before the list opens. Cancelable: canceling it keeps the list closed and leaves the decision to you.
+   * - `helix-clear`: Fired after the clear button has emptied the field, after `input` and `change`.
    * - `input`: Fired after the value changes.
    *
    * ## Slots
    *
    * Areas where markup can be added to the component.
    *
+   * - `clear-icon`: Replaces the cross on the clear button, under `clearable`.
    * - `end`: Content after the time, before the trigger, such as a clear button.
    * - `feedback`: The message that says what is wrong with the value.
    * - `hint`: Help under the field.
@@ -64939,6 +65293,7 @@ export type CustomElements = {
    *
    * Custom selectors for styling elements within the component.
    *
+   * - `clear`: The button that empties the field, under `clearable`, while it holds a time.
    * - `control`: The text input.
    * - `feedback`: The message that says what is wrong with the value.
    * - `field`: The box that holds the text and the trigger.
@@ -64984,6 +65339,7 @@ export type CustomElements = {
    * - `picker-option-item-selected`: The row of a chosen time: the one time, or either end of a range.
    * - `picker-option-label`: The option's label.
    * - `picker-option-text`: The label and the caption, as one column.
+   * - `range-separator`: The dash between a range's two rows of segments, in `segmented`, beside `literal`.
    * - `rest`: The count of times held beyond the ones shown. A `<button>` with `expandable`, and a `<span>` without it.
    * - `segment`: One part of the time, an hour, a minute, a second or AM and PM, in `segmented`.
    * - `segment-placeholder`: A segment with nothing in it yet. Applied with `segment`.
@@ -65004,6 +65360,7 @@ export type CustomElements = {
    *
    * These can be used to apply styling when a component is in a given state.
    *
+   * - `blank`: The field holds no time.
    * - `invalid`: The control has an error to show, from the browser's validation or from your `feedback`.
    * - `open`: While the clock is open.
    * - `settled`: Set one frame after the first render. Transitions wait for it, so an element does not animate its own arrival.
@@ -65259,6 +65616,12 @@ export type CustomElements = {
    *
    * Methods that can be called to access component functionality.
    *
+   * - `formResetCallback() => void`: Returns the control to its `defaultValue`, or to its `value` attribute
+   * where there is no `default-value`.
+   *
+   * Both halves are dropped, the consumer's and the control's, because a
+   * reset means the form is as it was served. Clearing only the internal one
+   * would leave a control that had been written to stuck at that value.
    * - `requestValue(next: string) => boolean`: Requests a new value, and returns whether the change was applied.
    *
    * Announces before it acts, so `preventDefault()` on the `helix-before-change` is
@@ -65266,12 +65629,6 @@ export type CustomElements = {
    * itself, whether or not a consumer declared `value`: a declared property
    * is a seed and a correction, the way `<input value>` is, and a consumer
    * who wants the change for themselves refuses it and assigns their own.
-   * - `formResetCallback() => void`: Returns the control to its `defaultValue`, or to its `value` attribute
-   * where there is no `default-value`.
-   *
-   * Both halves are dropped, the consumer's and the control's, because a
-   * reset means the form is as it was served. Clearing only the internal one
-   * would leave a control that had been written to stuck at that value.
    * - `formStateRestoreCallback(state: string | File | FormData | null) => void`: Restores the value when the browser brings a form back.
    *
    * Falling back to what the markup declared rather than to empty, because
@@ -65393,7 +65750,7 @@ export type CustomElements = {
    * - `list-loading`: The text shown while the options load.
    * - `list-search`: The region that holds the filter field.
    * - `list-search-field`: The filter field.
-   * - `option`: One time in the list. It carries `data-between` inside a range.
+   * - `option`: One time in the list. It carries `data-between` inside a range, and inside the run to the time under the pointer while a range waits for its second end.
    * - `option-between`: A time inside a chosen range, excluding its ends, beside `option`.
    * - `option-description`: The caption under the time's label, when there is one.
    * - `option-item`: The row.
@@ -65407,7 +65764,8 @@ export type CustomElements = {
    * These can be used to apply styling when a component is in a given state.
    *
    * - `blank`: While no time is chosen.
-   * - `invalid`: While `invalid` is set or `feedback` says what is wrong.
+   * - `invalid`: While `invalid` is set, `feedback` says what is wrong, or the list carries `aria-invalid`.
+   * - `range-pending`: While a `range` holds its first time and waits for the second.
    * - `settled`: Set one frame after the first render. Transitions wait for it, so an element does not animate its own arrival.
    */
   "helix-time-picker": Partial<
@@ -65962,6 +66320,11 @@ export type CustomElements = {
    * and this one was the English a form in another language still spoke in
    * the bubble it raises on submit: `feedback` replaces the message under
    * the field and does not reach that one.
+   * - `allow-empty-selection`/`allowEmptySelection`: Whether a press on the chosen item, or Space or Enter on it, takes it
+   * back so nothing is chosen, as React Aria's `ToggleButtonGroup` and
+   * Radix's `ToggleGroup` do in a single group. Absent, a single group always
+   * keeps its choice once it has one, as a radio group does. A multiple group
+   * releases a pressed item either way.
    * - `label-placement`/`labelPlacement`: Where the group's label sits. `start` puts it on the track's line.
    *
    * Absent is above, which is what a field looks like and what almost every
@@ -66282,7 +66645,7 @@ export type CustomElements = {
    *
    * These can be used to apply styling when a component is in a given state.
    *
-   * - `pressed`: The item is pressed, in a group where several can be.
+   * - `pressed`: The item is pressed, on its own or in a group where several can be.
    * - `selected`: The item is chosen.
    * - `settled`: Set one frame after the first render. Transitions wait for it, so an element does not animate its own arrival.
    */
@@ -74306,6 +74669,12 @@ export type CustomElementsSolidJs = {
    *
    * Methods that can be called to access component functionality.
    *
+   * - `formResetCallback() => void`: Returns the control to its `defaultValue`, or to its `value` attribute
+   * where there is no `default-value`.
+   *
+   * Both halves are dropped, the consumer's and the control's, because a
+   * reset means the form is as it was served. Clearing only the internal one
+   * would leave a control that had been written to stuck at that value.
    * - `requestValue(next: string) => boolean`: Requests a new value, and returns whether the change was applied.
    *
    * Announces before it acts, so `preventDefault()` on the `helix-before-change` is
@@ -74313,12 +74682,6 @@ export type CustomElementsSolidJs = {
    * itself, whether or not a consumer declared `value`: a declared property
    * is a seed and a correction, the way `<input value>` is, and a consumer
    * who wants the change for themselves refuses it and assigns their own.
-   * - `formResetCallback() => void`: Returns the control to its `defaultValue`, or to its `value` attribute
-   * where there is no `default-value`.
-   *
-   * Both halves are dropped, the consumer's and the control's, because a
-   * reset means the form is as it was served. Clearing only the internal one
-   * would leave a control that had been written to stuck at that value.
    * - `formStateRestoreCallback(state: string | File | FormData | null) => void`: Restores the value when the browser brings a form back.
    *
    * Falling back to what the markup declared rather than to empty, because
@@ -75743,6 +76106,10 @@ export type CustomElementsSolidJs = {
    * - `incomplete-message`/`incompleteMessage`: What a row of segments reports while some segments are set and others
    * are not, where `bad-input-message` is not set. `{kind}` is `date` or
    * `time`.
+   * - `range-end-label`/`rangeEndLabel`: What a screen reader hears before the segments of a range's second date
+   * or time, after each segment's own name.
+   * - `range-start-label`/`rangeStartLabel`: What a screen reader hears before the segments of a range's first date
+   * or time, after each segment's own name: "month, Start, Stay".
    * - `segmented`: Whether the field is a row of segments, one for each part of the date or
    * time, in place of a line of text.
    *
@@ -75827,27 +76194,39 @@ export type CustomElementsSolidJs = {
    * and this one was the English a form in another language still spoke in
    * the bubble it raises on submit: `feedback` replaces the message under
    * the field and does not reach that one.
-   * - `autocomplete`: What the browser may autofill here, as one of the platform's own tokens.
+   * - `autocomplete`: What the browser may autofill here, as one of the platform's own tokens,
+   * such as `bday`.
    *
    * Empty leaves the attribute off, which is the browser's default and is what
    * lets autofill work at all: hardcoding `off` here means a birthday or a
-   * postal code can never be filled in for a reader.
-   * - `calendar`: The calendar the written date and the calendar's days are in: `gregory`,
-   * `buddhist`, `japanese`, `roc`, or `iso8601`.
-   *
-   * Absent is the locale's own where it is one of the five, and `gregory` for
-   * every other, as Date Picker's `calendar` is. The value is `YYYY-MM-DD` in
-   * every calendar, and a focused field is ISO in every calendar. In
-   * `segmented`, the segments are the Gregorian day, month, and year, in the
-   * order the locale writes them, or ISO order for `iso8601`.
+   * postal code can never be filled in for a reader. With `segmented`, a
+   * hidden native date input carries it, since no browser fills the segments.
+   * - `calendar`: The calendar the written date, the segments, and the calendar's days are
+   * in: `gregory`, `buddhist`, `japanese`, `roc`, or `iso8601`, or a calendar
+   * with months of its own that Date Picker's `calendar` names, such as
+   * `persian`, `hebrew`, `islamic-umalqura`, `ethiopic`, or `chinese`.
+   *
+   * Absent is the locale's own where its months are the Gregorian months, and
+   * `gregory` for every other, as Date Picker's `calendar` is. The value is
+   * `YYYY-MM-DD` in every calendar, and a focused text field is ISO in every
+   * calendar. In `segmented`, the segments are the day, month, and year as
+   * the calendar counts them, in the order the locale writes them: Mehr 14,
+   * 1405 is month 7 and day 14 of 1405 under `persian`. Under the five with
+   * Gregorian months they are the Gregorian day, month, and year, or ISO order
+   * for `iso8601`.
    * - `calendar-label`/`calendarLabel`: The name of the calendar's grid of days, read by screen readers.
+   * - `clearable`: Whether the field shows a button that empties it, as Input's `clearable`
+   * does. Shown only while the field holds something to clear and is neither
+   * disabled nor read-only.
+   * - `clear-label`/`clearLabel`: The accessible name of the clear button, which shows only an icon.
    * - `date-style`/`dateStyle`: How a date is written in the field: `short` through `full`, or ISO.
    *
    * **The field renders when it is idle and holds the value when it is being
    * edited.** A written date is a rendering, and a document being edited must
    * not be a rendering of something else: `Intl.DateTimeFormat` formats and does
-   * not parse, so `4 August 2026` cannot be typed back, and writing a parser per
-   * locale is how a field ends up rejecting what it just displayed.
+   * not parse, so a rendering such as `Tuesday, August 4, 2026` is no text to
+   * edit. The field does read a date typed in the locale's order and digits as
+   * you leave it, which covers what a reader types.
    *
    * The way out is not to choose between the two but to separate them in time.
    * Idle, the field shows `4 August 2026`, which is what a date is for reading.
@@ -75915,6 +76294,9 @@ export type CustomElementsSolidJs = {
    *
    * **The name goes in**, so a row of them is heard as which one each
    * removes rather than as "Remove" said once per date.
+   * - `selection-label`/`selectionLabel`: What a screen reader hears about the dates chosen in the calendar, with
+   * `{kind}`, `{start}`, `{end}` and `{count}` filled in as Date Picker's
+   * `selection-label` says.
    * - `step`: How far apart the selectable dates are, in days.
    *
    * `<input type="date" step>`'s own unit, handed to the calendar this renders
@@ -75922,8 +76304,13 @@ export type CustomElementsSolidJs = {
    * where there is one and from 1 January 1970 where there is not, which is the
    * platform's base.
    * - `step-mismatch-message`/`stepMismatchMessage`: The message shown when a date is not on `step`.
+   * - `time-zone`/`timeZone`: The time zone today is read in, such as `America/New_York`, handed to the
+   * calendar: the day marked today, and the month an empty field opens on.
+   * Empty is the reader's own. Dates are plain `YYYY-MM-DD` and carry no zone.
    * - `trigger-label`/`triggerLabel`: The name of the button that opens the calendar, read by screen readers.
    * - `unavailable-message`/`unavailableMessage`: The message shown when `disable-dates` or `disable-days` bars a date.
+   * - `unreadable-message`/`unreadableMessage`: The message for text that is no date, where `bad-input-message` is not
+   * set. `{mode}` is `single`, `range`, or `multiple`.
    * - `year-view-label`/`yearViewLabel`: The name of the calendar's heading where it shows a page of years, with
    * `{heading}` filled in.
    * - `disabled`: Whether the control is disabled and cannot be used.
@@ -76003,12 +76390,14 @@ export type CustomElementsSolidJs = {
    * - `helix-before-change`: Fired before the date changes. Cancelable: call `preventDefault()` to keep the current date.
    * - `helix-before-close`: Fired before the calendar closes. Cancelable: call `preventDefault()` to keep it open.
    * - `helix-before-open`: Fired before the calendar opens. Cancelable: call `preventDefault()` to keep it closed.
+   * - `helix-clear`: Fired after the clear button has emptied the field, after `input` and `change`.
    * - `input`: Fired after the value changes.
    *
    * ## Slots
    *
    * Areas where markup can be added to the component.
    *
+   * - `clear-icon`: Replaces the cross on the clear button, under `clearable`.
    * - `end`: Content after the date, before the trigger, such as a clear button.
    * - `feedback`: The error message under the field.
    * - `hint`: The help text under the field.
@@ -76097,6 +76486,7 @@ export type CustomElementsSolidJs = {
    *
    * Custom selectors for styling elements within the component.
    *
+   * - `clear`: The button that empties the field, under `clearable`, while it holds a date.
    * - `control`: The text input.
    * - `date`: One held date, as a tag, in `multiple`.
    * - `date-cell`: The tag's grid cell, which a tag draws only inside a tag group.
@@ -76138,8 +76528,10 @@ export type CustomElementsSolidJs = {
    * - `picker-periods`: The grid of months or years.
    * - `picker-previous`: The control that moves to the previous month.
    * - `picker-previous-mark`: The icon on the previous month control.
+   * - `picker-selection`: The chosen date or range in words, which screen readers hear when it changes. Drawn for screen readers only.
    * - `picker-week`: One row of days.
    * - `picker-weekday`: A column header naming a day of the week.
+   * - `range-separator`: The dash between a range's two rows of segments, in `segmented`, beside `literal`.
    * - `rest`: The count of dates beyond the ones shown. It is a `<button>` with `expandable` and a `<span>` without it.
    * - `segment`: One part of the date, a year, a month or a day, in `segmented`.
    * - `segment-placeholder`: A segment with nothing in it yet. Applied with `segment`.
@@ -76153,6 +76545,7 @@ export type CustomElementsSolidJs = {
    *
    * These can be used to apply styling when a component is in a given state.
    *
+   * - `blank`: The field holds no date.
    * - `invalid`: The field has an error to show, from the browser's validation or from your `feedback`.
    * - `open`: The calendar is open.
    * - `settled`: Set one frame after the first render. Transitions wait for it, so an element does not animate its own arrival.
@@ -76217,14 +76610,16 @@ export type CustomElementsSolidJs = {
    * `ja-JP-u-ca-japanese`, and `gregory` for every other, such as `persian`
    * for `fa-IR`.
    *
-   * `persian`, `hebrew`, `islamic-umalqura`, `islamic-civil`, `ethiopic`,
-   * `coptic`, and `indian` draw a calendar with months of its own, as React
-   * Aria's calendars do: each grid is one of that calendar's months, the
-   * Hebrew leap month and Ethiopia's five-day thirteenth month included, and
-   * Previous, Next and the page keys move by those months. `month` and
+   * `persian`, `hebrew`, `islamic`, `islamic-umalqura`, `islamic-civil`,
+   * `islamic-tbla`, `islamic-rgsa`, `ethiopic`, `ethioaa`, `coptic`,
+   * `indian`, `chinese`, and `dangi` draw a calendar with months of its own,
+   * as React Aria's calendars do: each grid is one of that calendar's months,
+   * the Hebrew and Chinese leap months and Ethiopia's five-day thirteenth
+   * month included, and Previous, Next and the page keys move by those
+   * months. With `max-view`, the months view shows that calendar's year, of
+   * twelve or thirteen months, and the years view its years. `month` and
    * `helix-navigate` then name a month by its first day, `YYYY-MM-DD`. The
-   * heading stays text, as the months and years views are drawn in Gregorian
-   * months only. The value is `YYYY-MM-DD` in every calendar.
+   * value is `YYYY-MM-DD` in every calendar.
    * - `default-month`/`defaultMonth`: The month to open on when `month` is not set.
    * - `disable-dates`/`disableDates`: Dates that cannot be chosen, as `YYYY-MM-DD`, separated by commas or
    * spaces.
@@ -76287,6 +76682,11 @@ export type CustomElementsSolidJs = {
    * value and stays reachable, which is what a form showing a value somebody
    * else set needs.
    * - `required`: Stops the form from submitting while no date is chosen.
+   * - `selection-label`/`selectionLabel`: What a screen reader hears about the chosen dates: the grid's
+   * description, said again whenever the dates change. `{kind}` is `date`,
+   * `start` while a range holds one end, `range`, or `dates` for `multiple`.
+   * `{start}` and `{end}` are dates written in `locale`, and `{count}` is how
+   * many dates are chosen.
    * - `step`: How far apart the selectable dates are, in days.
    *
    * `<input type="date" step>`'s own unit, counted from `min` where there is
@@ -76415,6 +76815,12 @@ export type CustomElementsSolidJs = {
    *
    * Methods that can be called to access component functionality.
    *
+   * - `formResetCallback() => void`: Returns the control to its `defaultValue`, or to its `value` attribute
+   * where there is no `default-value`.
+   *
+   * Both halves are dropped, the consumer's and the control's, because a
+   * reset means the form is as it was served. Clearing only the internal one
+   * would leave a control that had been written to stuck at that value.
    * - `requestValue(next: string) => boolean`: Requests a new value, and returns whether the change was applied.
    *
    * Announces before it acts, so `preventDefault()` on the `helix-before-change` is
@@ -76422,18 +76828,19 @@ export type CustomElementsSolidJs = {
    * itself, whether or not a consumer declared `value`: a declared property
    * is a seed and a correction, the way `<input value>` is, and a consumer
    * who wants the change for themselves refuses it and assigns their own.
-   * - `formResetCallback() => void`: Returns the control to its `defaultValue`, or to its `value` attribute
-   * where there is no `default-value`.
-   *
-   * Both halves are dropped, the consumer's and the control's, because a
-   * reset means the form is as it was served. Clearing only the internal one
-   * would leave a control that had been written to stuck at that value.
    * - `formStateRestoreCallback(state: string | File | FormData | null) => void`: Restores the value when the browser brings a form back.
    *
    * Falling back to what the markup declared rather than to empty, because
    * a restore with no state is a form the browser has nothing recorded for,
    * which is the same situation as a fresh one.
    * - `focus(options?: FocusOptions) => void`: Moves focus to the control, as focusing a native control does.
+   * - `showChosen() => void`: Shows the days again, on the month of the chosen date, with the tab stop
+   * on that date, forgetting the month and the day the reader browsed to.
+   *
+   * Date Input calls it each time its panel opens, which is where the APG
+   * date picker dialog puts focus. Measured before this: from August 4, two
+   * presses of Page Down, Escape, and Down again opened on October 4.
+   * A `month` you set stays until the reader pages away from it.
    * - `formDisabledCallback(disabled: boolean) => void`: Called by the browser when an ancestor fieldset is disabled or enabled.
    *
    * **The argument is the effective state, and taking it whole is what latched
@@ -76483,6 +76890,7 @@ export type CustomElementsSolidJs = {
    * - `--date-picker-feedback-color`: The color of the message under the calendar, while `feedback` is set.
    * - `--date-picker-period-size`: Height of a month or a year in the months and years views, where `max-view` is set.
    * - `--date-picker-range-color`: Band behind the days in a range.
+   * - `--date-picker-range-preview-color`: Band behind the days a waiting range is drawn to, before its second end is chosen.
    * - `--date-picker-row-size`: Height of a week row.
    * - `--date-picker-selected-color`: Fill behind a selected day.
    * - `--date-picker-track-size`: Width of a column, which is what sets the space between days.
@@ -76493,7 +76901,7 @@ export type CustomElementsSolidJs = {
    * Custom selectors for styling elements within the component.
    *
    * - `cell`: One column of a week row. A range is painted on the cells.
-   * - `cell-range-end`: The cell of a range's last day, beside `cell`.
+   * - `cell-range-end`: The cell of a range's last day, beside `cell`, or of the day a waiting range is drawn to.
    * - `cell-range-middle`: A cell between a range's ends, beside `cell`.
    * - `cell-range-start`: The cell of a range's first day, beside `cell`.
    * - `day`: The shape inside a cell. A single chosen date is painted on it.
@@ -76519,6 +76927,7 @@ export type CustomElementsSolidJs = {
    * - `periods`: The grid of months or years.
    * - `previous`: The control that moves to the previous month.
    * - `previous-mark`: The glyph on the previous month control, where none is slotted.
+   * - `selection`: The chosen date or range in words, which screen readers hear when it changes. Drawn for screen readers only.
    * - `week`: One row of days.
    * - `weekday`: A column header naming a day of the week. It shows the short name and says the full one.
    *
@@ -76526,7 +76935,11 @@ export type CustomElementsSolidJs = {
    *
    * These can be used to apply styling when a component is in a given state.
    *
-   * - `invalid`: While `invalid` is set or `feedback` says what is wrong.
+   * - `blank`: While no date is chosen.
+   * - `invalid`: While `invalid` is set, `feedback` says what is wrong, the picker holds a date outside `min` and `max` or one it bars, or it is `required`, holds no date, and the reader has answered once or a form has refused it.
+   * - `month-view`: While the months of a year are shown, where `max-view` is set.
+   * - `range-pending`: While a `range` holds its first end and waits for the second.
+   * - `year-view`: While a page of years is shown, where `max-view` is `year`.
    * - `settled`: Set one frame after the first render. Transitions wait for it, so an element does not animate its own arrival.
    */
   "helix-date-picker": Partial<
@@ -79127,12 +79540,14 @@ export type CustomElementsSolidJs = {
    * Component attributes and properties that can be applied to the element or by using JavaScript.
    *
    * - `calendar`: The calendar a date is written in: `gregory`, `buddhist`, `japanese`,
-   * `roc`, or `iso8601`, the calendars Date Picker and Date Input draw.
-   *
-   * Absent is the locale's own where it is one of the five, such as
-   * `buddhist` for `th-TH`, and `gregory` for every other, such as `persian`
-   * for `fa-IR`, so a date written here reads as the same date a Date Picker
-   * beside it shows.
+   * `roc`, or `iso8601`, or a calendar with months of its own, such as
+   * `persian`, `hebrew`, `islamic-umalqura`, `ethiopic`, or `chinese`: every
+   * calendar Date Picker and Date Input draw.
+   *
+   * Absent is the locale's own where its months are the Gregorian months,
+   * such as `buddhist` for `th-TH`, and `gregory` for every other, such as
+   * `persian` for `fa-IR`, so a date written here reads as the same date a
+   * Date Picker beside it shows. Write `calendar="persian"` for Mehr 14, 1405.
    * - `date`: The timestamp, in any format `Date` can parse.
    *
    * An ISO string is what an API sends and what `<time datetime>` takes, so it
@@ -79151,6 +79566,9 @@ export type CustomElementsSolidJs = {
    * - `date-style`/`dateStyle`: The locale's own pattern for the date: `full`, `long`, `medium`, or
    * `short`. Set, it stands in for `weekday`, `day`, `month`, `year` and `era`.
    * - `day`: How the day of the month is written, where a date is shown.
+   * - `day-period`/`dayPeriod`: Writes the part of the day in words, such as "in the morning" or "at
+   * night", in its `long`, `short`, or `narrow` form, where `hour` is on a
+   * twelve-hour clock.
    * - `elapsed`: Shows how long ago the timestamp was, in a compact form such as "3h", in
    * place of the date.
    *
@@ -79165,6 +79583,8 @@ export type CustomElementsSolidJs = {
    * Off by default, which draws the date as one run of text, as Shoelace and
    * Web Awesome do. An `elapsed` or `relative` reading is one phrase either
    * way.
+   * - `fractional-second-digits`/`fractionalSecondDigits`: How many digits of a fraction of a second to write after `second`: 1, 2,
+   * or 3, as in 09:41:07.250.
    * - `frozen`: Draws an `elapsed` or `relative` reading once and leaves it, where it
    * would otherwise move on as it goes stale.
    *
@@ -79202,7 +79622,9 @@ export type CustomElementsSolidJs = {
    * - `time-zone`/`timeZone`: The time zone to read the timestamp in.
    *
    * Empty is the runtime's own.
-   * - `time-zone-name`/`timeZoneName`: Shows the name of the time zone, in its `long` or `short` form.
+   * - `time-zone-name`/`timeZoneName`: Shows the name of the time zone: `long` or `short`, as Pacific Daylight
+   * Time or PDT, `longOffset` or `shortOffset`, as GMT-07:00 or GMT-7, or
+   * `longGeneric` or `shortGeneric`, as Pacific Time or PT.
    * - `weekday`: How the weekday is written, where one is shown.
    * - `year`: How the year is written, where a date is shown.
    * - `whenSettled`: Resolves a frame after the first update, when transitions are switched on.
@@ -79233,6 +79655,7 @@ export type CustomElementsSolidJs = {
    * - `day`: The day of the month, with `fields`.
    * - `day-period`: AM or PM, or the locale's word for the part of the day, with `fields`.
    * - `era`: The era, such as AD, with `fields` and `era`.
+   * - `fractional-second`: The fraction of a second, with `fields` and `fractional-second-digits`.
    * - `hour`: The hour, with `fields`.
    * - `minute`: The minute, with `fields`.
    * - `month`: The month, with `fields`.
@@ -85038,6 +85461,7 @@ export type CustomElementsSolidJs = {
    * - `time-day`: Format Date's `day`, forwarded for a time drawn as fields. An elapsed time draws none.
    * - `time-day-period`: Format Date's `day-period`, forwarded for a time drawn as fields. An elapsed time draws none.
    * - `time-era`: Format Date's `era`, forwarded for a time drawn as fields. An elapsed time draws none.
+   * - `time-fractional-second`: Format Date's `fractional-second`, forwarded for a time drawn as fields. An elapsed time draws none.
    * - `time-hour`: Format Date's `hour`, forwarded for a time drawn as fields. An elapsed time draws none.
    * - `time-minute`: Format Date's `minute`, forwarded for a time drawn as fields. An elapsed time draws none.
    * - `time-month`: Format Date's `month`, forwarded for a time drawn as fields. An elapsed time draws none.
@@ -90214,6 +90638,9 @@ export type CustomElementsSolidJs = {
    * - `origin`: Where a single thumb's fill starts: `start` at `min`, `center` at the
    * middle of the track, or `end` at `max`. Absent is `start`. A range fills
    * between its thumbs and ignores it.
+   * - `page-step`/`pageStep`: How far Page Up and Page Down move a thumb, in the slider's own units, as
+   * React Aria's `pageSize` and Zag's `largeStep` do. Absent leaves the keys
+   * to the platform, which moves a tenth of the track.
    * - `range`: Adds a second thumb, so the value is a pair.
    *
    * The pair is one string, `"10,50"`, which is what `value` and
@@ -90421,6 +90848,8 @@ export type CustomElementsSolidJs = {
    *
    * These can be used to apply styling when a component is in a given state.
    *
+   * - `dragging`: A thumb is being dragged, by its thumb or from a press on the track.
+   * - `focus-visible`: A thumb has focus that the keyboard brought, where the browser draws a focus ring.
    * - `invalid`: The slider has an error to show, from the browser's validation or from your `feedback`.
    * - `settled`: Set one frame after the first render. Transitions wait for it, so an element does not animate its own arrival.
    */
@@ -93548,6 +93977,10 @@ export type CustomElementsSolidJs = {
    * - `incomplete-message`/`incompleteMessage`: What a row of segments reports while some segments are set and others
    * are not, where `bad-input-message` is not set. `{kind}` is `date` or
    * `time`.
+   * - `range-end-label`/`rangeEndLabel`: What a screen reader hears before the segments of a range's second date
+   * or time, after each segment's own name.
+   * - `range-start-label`/`rangeStartLabel`: What a screen reader hears before the segments of a range's first date
+   * or time, after each segment's own name: "month, Start, Stay".
    * - `segmented`: Whether the field is a row of segments, one for each part of the date or
    * time, in place of a line of text.
    *
@@ -93636,6 +94069,10 @@ export type CustomElementsSolidJs = {
    *
    * Empty leaves the attribute off, which is the browser's default and is what
    * lets autofill work at all.
+   * - `clearable`: Whether the field shows a button that empties it, as Input's `clearable`
+   * does. Shown only while the field holds something to clear and is neither
+   * disabled nor read-only.
+   * - `clear-label`/`clearLabel`: The accessible name of the clear button, which shows only an icon.
    * - `disable-times`/`disableTimes`: Times that cannot be chosen, as `HH:mm`, separated by commas or spaces.
    *
    * Handed to the list, which offers them as unavailable, and checked against
@@ -93684,6 +94121,8 @@ export type CustomElementsSolidJs = {
    * never something this element would refuse to read back.
    * - `trigger-label`/`triggerLabel`: The name of the button that opens the list, read by screen readers.
    * - `unavailable-message`/`unavailableMessage`: The message shown when `disable-times` bars a time.
+   * - `unreadable-message`/`unreadableMessage`: The message for text that is no time, where `bad-input-message` is not
+   * set. `{mode}` is `single`, `range`, or `multiple`, and `{shape}` is `HH:mm`, or `HH:mm:ss` with `seconds`.
    * - `variant`: Whether the panel shows one list of times or a column for each part of the
    * time.
    *
@@ -93766,12 +94205,14 @@ export type CustomElementsSolidJs = {
    * - `helix-before-change`: Fired before the time changes. Cancelable: canceling it stops the change and leaves the decision to you.
    * - `helix-before-close`: Fired before the list closes. Cancelable: canceling it keeps the list open and leaves the decision to you.
    * - `helix-before-open`: Fired before the list opens. Cancelable: canceling it keeps the list closed and leaves the decision to you.
+   * - `helix-clear`: Fired after the clear button has emptied the field, after `input` and `change`.
    * - `input`: Fired after the value changes.
    *
    * ## Slots
    *
    * Areas where markup can be added to the component.
    *
+   * - `clear-icon`: Replaces the cross on the clear button, under `clearable`.
    * - `end`: Content after the time, before the trigger, such as a clear button.
    * - `feedback`: The message that says what is wrong with the value.
    * - `hint`: Help under the field.
@@ -93858,6 +94299,7 @@ export type CustomElementsSolidJs = {
    *
    * Custom selectors for styling elements within the component.
    *
+   * - `clear`: The button that empties the field, under `clearable`, while it holds a time.
    * - `control`: The text input.
    * - `feedback`: The message that says what is wrong with the value.
    * - `field`: The box that holds the text and the trigger.
@@ -93903,6 +94345,7 @@ export type CustomElementsSolidJs = {
    * - `picker-option-item-selected`: The row of a chosen time: the one time, or either end of a range.
    * - `picker-option-label`: The option's label.
    * - `picker-option-text`: The label and the caption, as one column.
+   * - `range-separator`: The dash between a range's two rows of segments, in `segmented`, beside `literal`.
    * - `rest`: The count of times held beyond the ones shown. A `<button>` with `expandable`, and a `<span>` without it.
    * - `segment`: One part of the time, an hour, a minute, a second or AM and PM, in `segmented`.
    * - `segment-placeholder`: A segment with nothing in it yet. Applied with `segment`.
@@ -93923,6 +94366,7 @@ export type CustomElementsSolidJs = {
    *
    * These can be used to apply styling when a component is in a given state.
    *
+   * - `blank`: The field holds no time.
    * - `invalid`: The control has an error to show, from the browser's validation or from your `feedback`.
    * - `open`: While the clock is open.
    * - `settled`: Set one frame after the first render. Transitions wait for it, so an element does not animate its own arrival.
@@ -94181,6 +94625,12 @@ export type CustomElementsSolidJs = {
    *
    * Methods that can be called to access component functionality.
    *
+   * - `formResetCallback() => void`: Returns the control to its `defaultValue`, or to its `value` attribute
+   * where there is no `default-value`.
+   *
+   * Both halves are dropped, the consumer's and the control's, because a
+   * reset means the form is as it was served. Clearing only the internal one
+   * would leave a control that had been written to stuck at that value.
    * - `requestValue(next: string) => boolean`: Requests a new value, and returns whether the change was applied.
    *
    * Announces before it acts, so `preventDefault()` on the `helix-before-change` is
@@ -94188,12 +94638,6 @@ export type CustomElementsSolidJs = {
    * itself, whether or not a consumer declared `value`: a declared property
    * is a seed and a correction, the way `<input value>` is, and a consumer
    * who wants the change for themselves refuses it and assigns their own.
-   * - `formResetCallback() => void`: Returns the control to its `defaultValue`, or to its `value` attribute
-   * where there is no `default-value`.
-   *
-   * Both halves are dropped, the consumer's and the control's, because a
-   * reset means the form is as it was served. Clearing only the internal one
-   * would leave a control that had been written to stuck at that value.
    * - `formStateRestoreCallback(state: string | File | FormData | null) => void`: Restores the value when the browser brings a form back.
    *
    * Falling back to what the markup declared rather than to empty, because
@@ -94315,7 +94759,7 @@ export type CustomElementsSolidJs = {
    * - `list-loading`: The text shown while the options load.
    * - `list-search`: The region that holds the filter field.
    * - `list-search-field`: The filter field.
-   * - `option`: One time in the list. It carries `data-between` inside a range.
+   * - `option`: One time in the list. It carries `data-between` inside a range, and inside the run to the time under the pointer while a range waits for its second end.
    * - `option-between`: A time inside a chosen range, excluding its ends, beside `option`.
    * - `option-description`: The caption under the time's label, when there is one.
    * - `option-item`: The row.
@@ -94329,7 +94773,8 @@ export type CustomElementsSolidJs = {
    * These can be used to apply styling when a component is in a given state.
    *
    * - `blank`: While no time is chosen.
-   * - `invalid`: While `invalid` is set or `feedback` says what is wrong.
+   * - `invalid`: While `invalid` is set, `feedback` says what is wrong, or the list carries `aria-invalid`.
+   * - `range-pending`: While a `range` holds its first time and waits for the second.
    * - `settled`: Set one frame after the first render. Transitions wait for it, so an element does not animate its own arrival.
    */
   "helix-time-picker": Partial<
@@ -94904,6 +95349,11 @@ export type CustomElementsSolidJs = {
    * and this one was the English a form in another language still spoke in
    * the bubble it raises on submit: `feedback` replaces the message under
    * the field and does not reach that one.
+   * - `allow-empty-selection`/`allowEmptySelection`: Whether a press on the chosen item, or Space or Enter on it, takes it
+   * back so nothing is chosen, as React Aria's `ToggleButtonGroup` and
+   * Radix's `ToggleGroup` do in a single group. Absent, a single group always
+   * keeps its choice once it has one, as a radio group does. A multiple group
+   * releases a pressed item either way.
    * - `label-placement`/`labelPlacement`: Where the group's label sits. `start` puts it on the track's line.
    *
    * Absent is above, which is what a field looks like and what almost every
@@ -95227,7 +95677,7 @@ export type CustomElementsSolidJs = {
    *
    * These can be used to apply styling when a component is in a given state.
    *
-   * - `pressed`: The item is pressed, in a group where several can be.
+   * - `pressed`: The item is pressed, on its own or in a group where several can be.
    * - `selected`: The item is chosen.
    * - `settled`: Set one frame after the first render. Transitions wait for it, so an element does not animate its own arrival.
    */
@@ -97999,6 +98449,8 @@ export type CustomCssProperties = {
   "--date-picker-period-size"?: (string) | undefined;
   /** Band behind the days in a range. */
   "--date-picker-range-color"?: (string) | undefined;
+  /** Band behind the days a waiting range is drawn to, before its second end is chosen. */
+  "--date-picker-range-preview-color"?: (string) | undefined;
   /** Height of a week row. */
   "--date-picker-row-size"?: (string) | undefined;
   /** Fill behind a selected day. */