@fusion.dev/helix-headless 0.159.0 → 0.160.0

package/types/jsx.d.ts

@@ -9877,37 +9877,56 @@ export type HelixHeadlessDateInputHelixBeforeCloseElementEvent =
 /** `helix-before-open` event type */
 export type HelixHeadlessDateInputHelixBeforeOpenElementEvent =
   HelixHeadlessDateInputElementEvent<HelixBeforeOpenEvent>;
+/** `helix-clear` event type */
+export type HelixHeadlessDateInputHelixClearElementEvent =
+  HelixHeadlessDateInputElementEvent<HelixClearEvent>;
 /** `toggle` event type */
 export type HelixHeadlessDateInputToggleElementEvent =
   HelixHeadlessDateInputElementEvent<ToggleEvent>;
 
 export type HelixHeadlessDateInputProps = {
-  /** 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?: (HelixHeadlessDateInput["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?: (HelixHeadlessDateInput["calendar"]) | undefined;
   /** The name of the calendar's grid of days, read by screen readers. */
   "calendar-label"?: (HelixHeadlessDateInput["calendarLabel"]) | undefined;
   /** The name of the calendar's grid of days, read by screen readers. */
   calendarLabel?: (HelixHeadlessDateInput["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?: (HelixHeadlessDateInput["clearable"]) | undefined;
+  /** The accessible name of the clear button, which shows only an icon. */
+  "clear-label"?: (HelixHeadlessDateInput["clearLabel"]) | undefined;
+  /** The accessible name of the clear button, which shows only an icon. */
+  clearLabel?: (HelixHeadlessDateInput["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.
@@ -9929,8 +9948,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.
@@ -10068,6 +10088,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?: (HelixHeadlessDateInput["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"?: (HelixHeadlessDateInput["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?: (HelixHeadlessDateInput["selectionLabel"]) | undefined;
   /** How far apart the selectable dates are, in days.
 
 `<input type="date" step>`'s own unit, handed to the calendar this renders
@@ -10079,6 +10107,14 @@ platform's base. */
   "step-mismatch-message"?: (HelixHeadlessDateInput["stepMismatchMessage"]) | undefined;
   /** The message shown when a date is not on `step`. */
   stepMismatchMessage?: (HelixHeadlessDateInput["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"?: (HelixHeadlessDateInput["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?: (HelixHeadlessDateInput["timeZone"]) | undefined;
   /** The name of the button that opens the calendar, read by screen readers. */
   "trigger-label"?: (HelixHeadlessDateInput["triggerLabel"]) | undefined;
   /** The name of the button that opens the calendar, read by screen readers. */
@@ -10087,6 +10123,12 @@ platform's base. */
   "unavailable-message"?: (HelixHeadlessDateInput["unavailableMessage"]) | undefined;
   /** The message shown when `disable-dates` or `disable-days` bars a date. */
   unavailableMessage?: (HelixHeadlessDateInput["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"?: (HelixHeadlessDateInput["unreadableMessage"]) | undefined;
+  /** The message for text that is no date, where `bad-input-message` is not
+set. `{mode}` is `single`, `range`, or `multiple`. */
+  unreadableMessage?: (HelixHeadlessDateInput["unreadableMessage"]) | undefined;
   /** The name of the calendar's heading where it shows a page of years, with
 `{heading}` filled in. */
   "year-view-label"?: (HelixHeadlessDateInput["yearViewLabel"]) | undefined;
@@ -10115,6 +10157,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?: (HelixHeadlessDateInput["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"?: (HelixHeadlessDateInput["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?: (HelixHeadlessDateInput["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"?: (HelixHeadlessDateInput["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?: (HelixHeadlessDateInput["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.
 
@@ -10342,6 +10396,8 @@ reader makes in one of these. */
   "onhelix-before-open"?: ((
     e: HelixHeadlessDateInputHelixBeforeOpenElementEvent,
   ) => void) | undefined;
+  /** Fired after the clear button has emptied the field, after `input` and `change`. */
+  "onhelix-clear"?: ((e: HelixHeadlessDateInputHelixClearElementEvent) => void) | undefined;
   /** Fired after the value changes. */
   oninput?: ((e: HelixHeadlessDateInputElementEvent) => void) | undefined;
   /** Fired when the calendar opens or closes, with `newState` and `oldState`. */
@@ -10349,32 +10405,48 @@ reader makes in one of these. */
 };
 
 export type HelixHeadlessDateInputSolidJsProps = {
-  /** 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"?: (HelixHeadlessDateInput["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"?: (HelixHeadlessDateInput["calendar"]) | undefined;
   /** The name of the calendar's grid of days, read by screen readers. */
   "attr:calendar-label"?: (HelixHeadlessDateInput["calendarLabel"]) | undefined;
   /** The name of the calendar's grid of days, read by screen readers. */
   "prop:calendarLabel"?: (HelixHeadlessDateInput["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"?: (HelixHeadlessDateInput["clearable"]) | undefined;
+  /** The accessible name of the clear button, which shows only an icon. */
+  "attr:clear-label"?: (HelixHeadlessDateInput["clearLabel"]) | undefined;
+  /** The accessible name of the clear button, which shows only an icon. */
+  "prop:clearLabel"?: (HelixHeadlessDateInput["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.
@@ -10396,8 +10468,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.
@@ -10535,6 +10608,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"?: (HelixHeadlessDateInput["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"?: (HelixHeadlessDateInput["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"?: (HelixHeadlessDateInput["selectionLabel"]) | undefined;
   /** How far apart the selectable dates are, in days.
 
 `<input type="date" step>`'s own unit, handed to the calendar this renders
@@ -10546,6 +10627,14 @@ platform's base. */
   "attr:step-mismatch-message"?: (HelixHeadlessDateInput["stepMismatchMessage"]) | undefined;
   /** The message shown when a date is not on `step`. */
   "prop:stepMismatchMessage"?: (HelixHeadlessDateInput["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"?: (HelixHeadlessDateInput["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"?: (HelixHeadlessDateInput["timeZone"]) | undefined;
   /** The name of the button that opens the calendar, read by screen readers. */
   "attr:trigger-label"?: (HelixHeadlessDateInput["triggerLabel"]) | undefined;
   /** The name of the button that opens the calendar, read by screen readers. */
@@ -10554,6 +10643,12 @@ platform's base. */
   "attr:unavailable-message"?: (HelixHeadlessDateInput["unavailableMessage"]) | undefined;
   /** The message shown when `disable-dates` or `disable-days` bars a date. */
   "prop:unavailableMessage"?: (HelixHeadlessDateInput["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"?: (HelixHeadlessDateInput["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"?: (HelixHeadlessDateInput["unreadableMessage"]) | undefined;
   /** The name of the calendar's heading where it shows a page of years, with
 `{heading}` filled in. */
   "attr:year-view-label"?: (HelixHeadlessDateInput["yearViewLabel"]) | undefined;
@@ -10582,6 +10677,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"?: (HelixHeadlessDateInput["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"?: (HelixHeadlessDateInput["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"?: (HelixHeadlessDateInput["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"?: (HelixHeadlessDateInput["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"?: (HelixHeadlessDateInput["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.
 
@@ -10808,6 +10915,8 @@ reader makes in one of these. */
   "on:helix-before-open"?: ((
     e: HelixHeadlessDateInputHelixBeforeOpenElementEvent,
   ) => void) | undefined;
+  /** Fired after the clear button has emptied the field, after `input` and `change`. */
+  "on:helix-clear"?: ((e: HelixHeadlessDateInputHelixClearElementEvent) => void) | undefined;
   /** Fired after the value changes. */
   "on:input"?: ((e: HelixHeadlessDateInputElementEvent) => void) | undefined;
   /** Fired when the calendar opens or closes, with `newState` and `oldState`. */
@@ -10856,14 +10965,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?: (HelixHeadlessDatePicker["calendar"]) | undefined;
   /** The month to open on when `month` is not set. */
   "default-month"?: (HelixHeadlessDatePicker["defaultMonth"]) | undefined;
@@ -11010,6 +11121,18 @@ else set needs. */
   readOnly?: (HelixHeadlessDatePicker["readOnly"]) | undefined;
   /** Stops the form from submitting while no date is chosen. */
   required?: (HelixHeadlessDatePicker["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"?: (HelixHeadlessDatePicker["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?: (HelixHeadlessDatePicker["selectionLabel"]) | undefined;
   /** How far apart the selectable dates are, in days.
 
 `<input type="date" step>`'s own unit, counted from `min` where there is
@@ -11189,14 +11312,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"?: (HelixHeadlessDatePicker["calendar"]) | undefined;
   /** The month to open on when `month` is not set. */
   "attr:default-month"?: (HelixHeadlessDatePicker["defaultMonth"]) | undefined;
@@ -11343,6 +11468,18 @@ else set needs. */
   "prop:readOnly"?: (HelixHeadlessDatePicker["readOnly"]) | undefined;
   /** Stops the form from submitting while no date is chosen. */
   "prop:required"?: (HelixHeadlessDatePicker["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"?: (HelixHeadlessDatePicker["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"?: (HelixHeadlessDatePicker["selectionLabel"]) | undefined;
   /** How far apart the selectable dates are, in days.
 
 `<input type="date" step>`'s own unit, counted from `min` where there is
@@ -13840,12 +13977,14 @@ Here rather than on each control. */
 
 export type HelixHeadlessFormatDateProps = {
   /** 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?: (HelixHeadlessFormatDate["calendar"]) | undefined;
   /** The timestamp, in any format `Date` can parse.
 
@@ -13871,6 +14010,14 @@ browser may use either. */
   dateStyle?: (HelixHeadlessFormatDate["dateStyle"]) | undefined;
   /** How the day of the month is written, where a date is shown. */
   day?: (HelixHeadlessFormatDate["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"?: (HelixHeadlessFormatDate["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?: (HelixHeadlessFormatDate["dayPeriod"]) | undefined;
   /** Shows how long ago the timestamp was, in a compact form such as "3h", in
 place of the date.
 
@@ -13888,6 +14035,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?: (HelixHeadlessFormatDate["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"?: (HelixHeadlessFormatDate["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?: (HelixHeadlessFormatDate["fractionalSecondDigits"]) | undefined;
   /** Draws an `elapsed` or `relative` reading once and leaves it, where it
 would otherwise move on as it goes stale.
 
@@ -13950,9 +14103,13 @@ Empty is the runtime's own. */
 
 Empty is the runtime's own. */
   timeZone?: (HelixHeadlessFormatDate["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"?: (HelixHeadlessFormatDate["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?: (HelixHeadlessFormatDate["timeZoneName"]) | undefined;
   /** How the weekday is written, where one is shown. */
   weekday?: (HelixHeadlessFormatDate["weekday"]) | undefined;
@@ -13962,12 +14119,14 @@ Empty is the runtime's own. */
 
 export type HelixHeadlessFormatDateSolidJsProps = {
   /** 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"?: (HelixHeadlessFormatDate["calendar"]) | undefined;
   /** The timestamp, in any format `Date` can parse.
 
@@ -13993,6 +14152,14 @@ browser may use either. */
   "prop:dateStyle"?: (HelixHeadlessFormatDate["dateStyle"]) | undefined;
   /** How the day of the month is written, where a date is shown. */
   "prop:day"?: (HelixHeadlessFormatDate["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"?: (HelixHeadlessFormatDate["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"?: (HelixHeadlessFormatDate["dayPeriod"]) | undefined;
   /** Shows how long ago the timestamp was, in a compact form such as "3h", in
 place of the date.
 
@@ -14010,6 +14177,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"?: (HelixHeadlessFormatDate["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"?: (HelixHeadlessFormatDate["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"?: (HelixHeadlessFormatDate["fractionalSecondDigits"]) | undefined;
   /** Draws an `elapsed` or `relative` reading once and leaves it, where it
 would otherwise move on as it goes stale.
 
@@ -14072,9 +14245,13 @@ Empty is the runtime's own. */
 
 Empty is the runtime's own. */
   "prop:timeZone"?: (HelixHeadlessFormatDate["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"?: (HelixHeadlessFormatDate["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"?: (HelixHeadlessFormatDate["timeZoneName"]) | undefined;
   /** How the weekday is written, where one is shown. */
   "prop:weekday"?: (HelixHeadlessFormatDate["weekday"]) | undefined;
@@ -26355,6 +26532,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?: (HelixHeadlessSlider["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"?: (HelixHeadlessSlider["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?: (HelixHeadlessSlider["pageStep"]) | undefined;
   /** Adds a second thumb, so the value is a pair.
 
 The pair is one string, `"10,50"`, which is what `value` and
@@ -26609,6 +26794,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"?: (HelixHeadlessSlider["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"?: (HelixHeadlessSlider["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"?: (HelixHeadlessSlider["pageStep"]) | undefined;
   /** Adds a second thumb, so the value is a pair.
 
 The pair is one string, `"10,50"`, which is what `value` and
@@ -30193,6 +30386,9 @@ export type HelixHeadlessTimeInputHelixBeforeCloseElementEvent =
 /** `helix-before-open` event type */
 export type HelixHeadlessTimeInputHelixBeforeOpenElementEvent =
   HelixHeadlessTimeInputElementEvent<HelixBeforeOpenEvent>;
+/** `helix-clear` event type */
+export type HelixHeadlessTimeInputHelixClearElementEvent =
+  HelixHeadlessTimeInputElementEvent<HelixClearEvent>;
 /** `toggle` event type */
 export type HelixHeadlessTimeInputToggleElementEvent =
   HelixHeadlessTimeInputElementEvent<ToggleEvent>;
@@ -30203,6 +30399,14 @@ export type HelixHeadlessTimeInputProps = {
 Empty leaves the attribute off, which is the browser's default and is what
 lets autofill work at all. */
   autocomplete?: (HelixHeadlessTimeInput["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?: (HelixHeadlessTimeInput["clearable"]) | undefined;
+  /** The accessible name of the clear button, which shows only an icon. */
+  "clear-label"?: (HelixHeadlessTimeInput["clearLabel"]) | undefined;
+  /** The accessible name of the clear button, which shows only an icon. */
+  clearLabel?: (HelixHeadlessTimeInput["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
@@ -30306,6 +30510,12 @@ never something this element would refuse to read back. */
   "unavailable-message"?: (HelixHeadlessTimeInput["unavailableMessage"]) | undefined;
   /** The message shown when `disable-times` bars a time. */
   unavailableMessage?: (HelixHeadlessTimeInput["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"?: (HelixHeadlessTimeInput["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?: (HelixHeadlessTimeInput["unreadableMessage"]) | undefined;
   /** Whether the panel shows one list of times or a column for each part of the
 time.
 
@@ -30343,6 +30553,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?: (HelixHeadlessTimeInput["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"?: (HelixHeadlessTimeInput["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?: (HelixHeadlessTimeInput["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"?: (HelixHeadlessTimeInput["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?: (HelixHeadlessTimeInput["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.
 
@@ -30559,6 +30781,8 @@ a consumer handing over `new Date()` gets the time of day they expected. */
   "onhelix-before-open"?: ((
     e: HelixHeadlessTimeInputHelixBeforeOpenElementEvent,
   ) => void) | undefined;
+  /** Fired after the clear button has emptied the field, after `input` and `change`. */
+  "onhelix-clear"?: ((e: HelixHeadlessTimeInputHelixClearElementEvent) => void) | undefined;
   /** Fired after the value changes. */
   oninput?: ((e: HelixHeadlessTimeInputElementEvent) => void) | undefined;
   /** Fired after the list opens or closes, with `newState` and `oldState`. */
@@ -30571,6 +30795,14 @@ export type HelixHeadlessTimeInputSolidJsProps = {
 Empty leaves the attribute off, which is the browser's default and is what
 lets autofill work at all. */
   "prop:autocomplete"?: (HelixHeadlessTimeInput["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"?: (HelixHeadlessTimeInput["clearable"]) | undefined;
+  /** The accessible name of the clear button, which shows only an icon. */
+  "attr:clear-label"?: (HelixHeadlessTimeInput["clearLabel"]) | undefined;
+  /** The accessible name of the clear button, which shows only an icon. */
+  "prop:clearLabel"?: (HelixHeadlessTimeInput["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
@@ -30674,6 +30906,12 @@ never something this element would refuse to read back. */
   "attr:unavailable-message"?: (HelixHeadlessTimeInput["unavailableMessage"]) | undefined;
   /** The message shown when `disable-times` bars a time. */
   "prop:unavailableMessage"?: (HelixHeadlessTimeInput["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"?: (HelixHeadlessTimeInput["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"?: (HelixHeadlessTimeInput["unreadableMessage"]) | undefined;
   /** Whether the panel shows one list of times or a column for each part of the
 time.
 
@@ -30711,6 +30949,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"?: (HelixHeadlessTimeInput["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"?: (HelixHeadlessTimeInput["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"?: (HelixHeadlessTimeInput["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"?: (HelixHeadlessTimeInput["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"?: (HelixHeadlessTimeInput["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.
 
@@ -30926,6 +31176,8 @@ a consumer handing over `new Date()` gets the time of day they expected. */
   "on:helix-before-open"?: ((
     e: HelixHeadlessTimeInputHelixBeforeOpenElementEvent,
   ) => void) | undefined;
+  /** Fired after the clear button has emptied the field, after `input` and `change`. */
+  "on:helix-clear"?: ((e: HelixHeadlessTimeInputHelixClearElementEvent) => void) | undefined;
   /** Fired after the value changes. */
   "on:input"?: ((e: HelixHeadlessTimeInputElementEvent) => void) | undefined;
   /** Fired after the list opens or closes, with `newState` and `oldState`. */
@@ -31920,6 +32172,18 @@ export type HelixHeadlessToggleGroupHelixSelectElementEvent =
   HelixHeadlessToggleGroupElementEvent<HelixSelectEvent>;
 
 export type HelixHeadlessToggleGroupProps = {
+  /** 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"?: (HelixHeadlessToggleGroup["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?: (HelixHeadlessToggleGroup["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
@@ -32098,6 +32362,18 @@ Where one item is chosen, it is that one value, or none. */
 };
 
 export type HelixHeadlessToggleGroupSolidJsProps = {
+  /** 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"?: (HelixHeadlessToggleGroup["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"?: (HelixHeadlessToggleGroup["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
@@ -42319,17 +42595,24 @@ export type CustomElements = {
    * gives a picker and locale formatting but allows almost no styling, so the
    * field is a text field. Typing sends `input` on each keystroke and `change`
    * when you leave the field, as a text field does. A date picked from the
-   * calendar sends both.
+   * calendar sends both. The field reads ISO, `2026-08-04`, and a date written
+   * in the order, the digits, and the month names of `locale`, `8/4/2026` or
+   * `Aug 4, 2026` in `en-US` and `4.8.2026` in `de-DE`, which becomes the value
+   * as you leave the field.
    *
    * The trigger and ArrowDown open the calendar with focus on the selected day,
    * Tab moves between the calendar's controls without leaving it, and Escape
    * closes it and returns focus to the field. A press into the field opens the
    * calendar too. Tab into the field opens nothing, and Tab out of the field
-   * closes the calendar.
+   * closes the calendar. The text field is a `combobox` with
+   * `aria-haspopup="dialog"`, `aria-expanded`, and `aria-controls`, as in the
+   * APG date picker combobox, since Down opens the calendar from it.
    *
    * With `segmented`, the field is a row of segments in place of the text: a
    * month, a day and a year in the order the locale writes them, each set with
-   * digits or the arrow keys. Alt+Down opens the calendar from a segment.
+   * digits or the arrow keys. Alt+Down opens the calendar from a segment. A
+   * `range` is two rows with a dash between them, the start and the end, as
+   * React Aria's DateRangePicker draws them, and `multiple` keeps the text.
    *
    * Text that is not a date gives the form an empty value, as a native date
    * field does, and `value` keeps the text so it can be corrected.
@@ -42359,27 +42642,39 @@ export type CustomElements = {
    *
    * Component attributes and properties that can be applied to the element or by using JavaScript.
    *
-   * - `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.
@@ -42447,6 +42742,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
@@ -42454,8 +42752,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.
    * - `empty-message`/`emptyMessage`: What a row of segments reports when the field is required and every
@@ -42466,6 +42769,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.
    *
@@ -42626,6 +42933,7 @@ 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.
    * - `toggle`: Fired when the calendar opens or closes, with `newState` and `oldState`.
    *
@@ -42633,6 +42941,7 @@ export type CustomElements = {
    *
    * 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.
@@ -42708,6 +43017,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.
@@ -42749,8 +43059,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`.
@@ -42764,6 +43076,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.
@@ -42783,9 +43096,11 @@ export type CustomElements = {
    * **Dates are `YYYY-MM-DD` strings, and every calculation is in UTC**, because
    * a local-time `Date` shifts across a time zone or daylight-saving boundary.
    *
-   * **The days are the Gregorian calendar's**, written in `calendar`: the
-   * locale's own where its months are the Gregorian months, as `th-TH` writes
-   * 2569 for 2026, and `gregory` where they are not, as for `fa-IR`.
+   * **The months are the ones `calendar` counts**: the Gregorian months for the
+   * locale's own calendar where its months are the Gregorian months, as `th-TH`
+   * writes 2569 for 2026, and `gregory` where they are not, as for `fa-IR`
+   * with no `calendar`. Name a calendar with months of its own, such as
+   * `persian`, and every view counts its days, months, and years from `Intl`.
    *
    * `month` sets which month the grid shows, separately from `value`, so paging
    * selects nothing and you can control the view. When unset, it follows the
@@ -42793,7 +43108,14 @@ export type CustomElements = {
    *
    * `mode` sets how many dates are held. Unset holds one, `range` holds two and
    * marks the dates between them, and `multiple` toggles each date. All three
-   * read and write the same comma-separated `value`.
+   * read and write the same comma-separated `value`. With a `mode`, the grid
+   * carries `aria-multiselectable`. While a range holds one end, the grid draws
+   * the range to the day under the pointer or the focus, marking those cells
+   * `data-range-preview`.
+   *
+   * The chosen date, range, or count of dates is the grid's description, in a
+   * region screen readers announce when it changes, as React Aria's calendars
+   * do. `selection-label` words it.
    *
    * `max-view` makes the heading a button that steps back to the months of the
    * year, and with `year` to a page of years, as Zag's date picker does. The
@@ -42828,14 +43150,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.
@@ -42898,6 +43222,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
@@ -43052,6 +43381,13 @@ export type CustomElements = {
    * Date Input calls this when its trigger opens the calendar, which is where
    * the APG date picker dialog puts focus. The host is not focusable, so a
    * plain `focus()` on it did nothing and focus stayed on the trigger.
+   * - `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.
    * - `requestValue(next: string) => boolean`: Refuses every change while read-only. See `readOnly`.
    * - `formResetCallback() => void`: Returns the control to its `defaultValue`, or to its `value` attribute
    * where there is no `default-value`.
@@ -43115,7 +43451,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.
@@ -43141,6 +43477,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.
    *
@@ -43148,7 +43485,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-headless-date-picker": Partial<
@@ -45762,20 +46103,22 @@ export type CustomElements = {
    *
    * **A date is written in a calendar Date Picker draws**: the locale's own
    * where its months are the Gregorian months, as `th-TH` writes 2569 for 2026,
-   * and `gregory` where they are not, as for `fa-IR`. `calendar` picks one of
-   * the five.
+   * and `gregory` where they are not, as for `fa-IR`. `calendar` picks any of
+   * them, `persian` and `hebrew` included.
    *
    * ## Attributes & Properties
    *
    * 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
@@ -45794,6 +46137,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.
    *
@@ -45808,6 +46154,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.
    *
@@ -45845,7 +46193,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.
@@ -45876,6 +46226,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`.
@@ -51633,6 +51984,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.
@@ -56010,6 +56362,10 @@ export type CustomElements = {
    * `min-steps-between-thumbs` keeps them that many steps apart, and the readout
    * joins the two as `range-text` writes them.
    *
+   * A press on a range's track takes the nearest thumb to the point pressed,
+   * and moving the pointer drags it, as React Aria's and Web Awesome's sliders
+   * do. The thumb takes focus, and `change` is sent as the press ends.
+   *
    * `origin` sets where a single thumb's fill starts: at `min`, at the middle of
    * the track, or at `max`. A balance or an offset from zero fills from the
    * middle, as Zag's slider `origin` does. The fill's ends are published as
@@ -56034,7 +56390,7 @@ export type CustomElements = {
    * |---|---|
    * | Right, Up | Moves the thumb up by `step`. |
    * | Left, Down | Moves the thumb down by `step`. |
-   * | Page Up, Page Down | Moves the thumb by a larger step. |
+   * | Page Up, Page Down | Moves the thumb by `page-step`, or by the platform's larger step where it is not set. |
    * | Home, End | Moves the thumb to its lowest or highest value. |
    *
    * Under `readonly` none of these move the thumb, and Tab still reaches it.
@@ -56095,6 +56451,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
@@ -56327,6 +56686,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.
    */
@@ -59451,20 +59812,25 @@ export type CustomElements = {
    * `seconds`, because that is what the form
    * submits, what `min` and `max` compare against, and what sorts correctly as a
    * string. While idle, the field shows the time in the user's locale format.
-   * Once the caret is in the field, it shows the value itself, because a
-   * formatted time such as `2:30 PM` cannot be typed back and `Intl` has no
-   * parser for it.
+   * Once the caret is in the field, it shows the value itself. You can type
+   * `14:30`, or a time as you write one, such as `2:30 PM`, `2.30pm`, or
+   * `14h30`, and the field reads it as you leave it, with AM and PM in the
+   * locale's words.
    *
    * Typing sends `input` on each keystroke and `change` when you leave the
    * field. The trigger and ArrowDown open the list, and so does a press into the
-   * field; Tab into the field opens nothing. In the list, the arrow keys, typed digits and PageUp and PageDown
+   * field; Tab into the field opens nothing. The text field is a `combobox`
+   * with `aria-haspopup="dialog"`, `aria-expanded`, and `aria-controls`, since
+   * Down opens the list from it. In the list, the arrow keys, typed digits and PageUp and PageDown
    * move through the times, and Enter, Space or a click chooses one and closes
    * the panel. With `variant="wheels"` each wheel moves the time as you turn it,
    * the panel stays open, and Enter or Escape closes it.
    *
    * With `segmented`, the field is a row of segments in place of the text: an
    * hour, a minute, and AM or PM where the clock has them, each set with digits
-   * or the arrow keys. Alt+Down opens the list from a segment.
+   * or the arrow keys. Alt+Down opens the list from a segment. A `range` is two
+   * rows with a dash between them, the start and the end, and `multiple` keeps
+   * the text.
    *
    * Text that is not a time gives the form an empty value, as a native time
    * field does, and `value` keeps the text so it can be corrected.
@@ -59496,6 +59862,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
@@ -59544,6 +59914,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.
    *
@@ -59566,6 +59938,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.
    *
@@ -59717,6 +60093,7 @@ 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.
    * - `toggle`: Fired after the list opens or closes, with `newState` and `oldState`.
    *
@@ -59724,6 +60101,7 @@ export type CustomElements = {
    *
    * 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.
@@ -59797,6 +60175,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.
@@ -59842,6 +60221,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`.
@@ -59862,6 +60242,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.
@@ -59915,7 +60296,10 @@ export type CustomElements = {
    * host's `aria-label` or its `aria-labelledby`. A development build warns
    * where all four are empty. The list is described by the hint, or by the
    * message in `feedback` in its place, and carries `aria-multiselectable` with
-   * a `mode` and `aria-invalid` while `feedback` says what is wrong. The wheels
+   * a `mode`. It carries `aria-invalid` while `feedback` says what is wrong,
+   * while it holds a time outside `min` and `max` or one the picker does not
+   * offer, and, for a `required` picker with no time, once the reader has
+   * chosen one or a form has refused the picker. The wheels
    * are a `group` with that name, holding one `listbox` per wheel, named "Hour",
    * "Minute", "Second" and "AM/PM" in the page's language, and each described
    * the same way.
@@ -60273,7 +60657,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.
@@ -60287,7 +60671,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-headless-time-picker": Partial<
@@ -60871,7 +61256,7 @@ export type CustomElements = {
    * | Right, Down | Moves to the next item, from the last back to the first. In a single group, chooses it. |
    * | Left, Up | Moves to the item before, from the first round to the last. In a single group, chooses it. |
    * | Home, End | Moves to the first or the last item. In a single group, chooses it. |
-   * | Space, Enter | Chooses the focused item, or presses or releases it in a multiple group. |
+   * | Space, Enter | Chooses the focused item, or presses or releases it in a multiple group. With `allow-empty-selection`, takes back the chosen item. |
    *
    * Left and Right swap on a right-to-left page, and a disabled item is passed
    * over. A single group is a `radiogroup` of items with `role="radio"` and
@@ -60883,6 +61268,11 @@ export type CustomElements = {
    *
    * Component attributes and properties that can be applied to the element or by using JavaScript.
    *
+   * - `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
@@ -61227,13 +61617,13 @@ export type CustomElements = {
    *
    * Custom selectors for styling elements within the component.
    *
-   * - `item`: The radio button.
+   * - `item`: The button: a radio in a group where one is chosen, and a button with `aria-pressed` on its own or in a group where several can be.
    *
    * ## CSS States
    *
    * 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.
    */
@@ -70673,17 +71063,24 @@ export type CustomElementsSolidJs = {
    * gives a picker and locale formatting but allows almost no styling, so the
    * field is a text field. Typing sends `input` on each keystroke and `change`
    * when you leave the field, as a text field does. A date picked from the
-   * calendar sends both.
+   * calendar sends both. The field reads ISO, `2026-08-04`, and a date written
+   * in the order, the digits, and the month names of `locale`, `8/4/2026` or
+   * `Aug 4, 2026` in `en-US` and `4.8.2026` in `de-DE`, which becomes the value
+   * as you leave the field.
    *
    * The trigger and ArrowDown open the calendar with focus on the selected day,
    * Tab moves between the calendar's controls without leaving it, and Escape
    * closes it and returns focus to the field. A press into the field opens the
    * calendar too. Tab into the field opens nothing, and Tab out of the field
-   * closes the calendar.
+   * closes the calendar. The text field is a `combobox` with
+   * `aria-haspopup="dialog"`, `aria-expanded`, and `aria-controls`, as in the
+   * APG date picker combobox, since Down opens the calendar from it.
    *
    * With `segmented`, the field is a row of segments in place of the text: a
    * month, a day and a year in the order the locale writes them, each set with
-   * digits or the arrow keys. Alt+Down opens the calendar from a segment.
+   * digits or the arrow keys. Alt+Down opens the calendar from a segment. A
+   * `range` is two rows with a dash between them, the start and the end, as
+   * React Aria's DateRangePicker draws them, and `multiple` keeps the text.
    *
    * Text that is not a date gives the form an empty value, as a native date
    * field does, and `value` keeps the text so it can be corrected.
@@ -70713,27 +71110,39 @@ export type CustomElementsSolidJs = {
    *
    * Component attributes and properties that can be applied to the element or by using JavaScript.
    *
-   * - `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.
@@ -70801,6 +71210,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
@@ -70808,8 +71220,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.
    * - `empty-message`/`emptyMessage`: What a row of segments reports when the field is required and every
@@ -70820,6 +71237,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.
    *
@@ -70980,6 +71401,7 @@ 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.
    * - `toggle`: Fired when the calendar opens or closes, with `newState` and `oldState`.
    *
@@ -70987,6 +71409,7 @@ export type CustomElementsSolidJs = {
    *
    * 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.
@@ -71062,6 +71485,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.
@@ -71103,8 +71527,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`.
@@ -71118,6 +71544,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.
@@ -71140,9 +71567,11 @@ export type CustomElementsSolidJs = {
    * **Dates are `YYYY-MM-DD` strings, and every calculation is in UTC**, because
    * a local-time `Date` shifts across a time zone or daylight-saving boundary.
    *
-   * **The days are the Gregorian calendar's**, written in `calendar`: the
-   * locale's own where its months are the Gregorian months, as `th-TH` writes
-   * 2569 for 2026, and `gregory` where they are not, as for `fa-IR`.
+   * **The months are the ones `calendar` counts**: the Gregorian months for the
+   * locale's own calendar where its months are the Gregorian months, as `th-TH`
+   * writes 2569 for 2026, and `gregory` where they are not, as for `fa-IR`
+   * with no `calendar`. Name a calendar with months of its own, such as
+   * `persian`, and every view counts its days, months, and years from `Intl`.
    *
    * `month` sets which month the grid shows, separately from `value`, so paging
    * selects nothing and you can control the view. When unset, it follows the
@@ -71150,7 +71579,14 @@ export type CustomElementsSolidJs = {
    *
    * `mode` sets how many dates are held. Unset holds one, `range` holds two and
    * marks the dates between them, and `multiple` toggles each date. All three
-   * read and write the same comma-separated `value`.
+   * read and write the same comma-separated `value`. With a `mode`, the grid
+   * carries `aria-multiselectable`. While a range holds one end, the grid draws
+   * the range to the day under the pointer or the focus, marking those cells
+   * `data-range-preview`.
+   *
+   * The chosen date, range, or count of dates is the grid's description, in a
+   * region screen readers announce when it changes, as React Aria's calendars
+   * do. `selection-label` words it.
    *
    * `max-view` makes the heading a button that steps back to the months of the
    * year, and with `year` to a page of years, as Zag's date picker does. The
@@ -71185,14 +71621,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.
@@ -71255,6 +71693,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
@@ -71409,6 +71852,13 @@ export type CustomElementsSolidJs = {
    * Date Input calls this when its trigger opens the calendar, which is where
    * the APG date picker dialog puts focus. The host is not focusable, so a
    * plain `focus()` on it did nothing and focus stayed on the trigger.
+   * - `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.
    * - `requestValue(next: string) => boolean`: Refuses every change while read-only. See `readOnly`.
    * - `formResetCallback() => void`: Returns the control to its `defaultValue`, or to its `value` attribute
    * where there is no `default-value`.
@@ -71472,7 +71922,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.
@@ -71498,6 +71948,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.
    *
@@ -71505,7 +71956,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-headless-date-picker": Partial<
@@ -74147,20 +74602,22 @@ export type CustomElementsSolidJs = {
    *
    * **A date is written in a calendar Date Picker draws**: the locale's own
    * where its months are the Gregorian months, as `th-TH` writes 2569 for 2026,
-   * and `gregory` where they are not, as for `fa-IR`. `calendar` picks one of
-   * the five.
+   * and `gregory` where they are not, as for `fa-IR`. `calendar` picks any of
+   * them, `persian` and `hebrew` included.
    *
    * ## Attributes & Properties
    *
    * 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
@@ -74179,6 +74636,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.
    *
@@ -74193,6 +74653,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.
    *
@@ -74230,7 +74692,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.
@@ -74261,6 +74725,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`.
@@ -80098,6 +80563,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.
@@ -84523,6 +84989,10 @@ export type CustomElementsSolidJs = {
    * `min-steps-between-thumbs` keeps them that many steps apart, and the readout
    * joins the two as `range-text` writes them.
    *
+   * A press on a range's track takes the nearest thumb to the point pressed,
+   * and moving the pointer drags it, as React Aria's and Web Awesome's sliders
+   * do. The thumb takes focus, and `change` is sent as the press ends.
+   *
    * `origin` sets where a single thumb's fill starts: at `min`, at the middle of
    * the track, or at `max`. A balance or an offset from zero fills from the
    * middle, as Zag's slider `origin` does. The fill's ends are published as
@@ -84547,7 +85017,7 @@ export type CustomElementsSolidJs = {
    * |---|---|
    * | Right, Up | Moves the thumb up by `step`. |
    * | Left, Down | Moves the thumb down by `step`. |
-   * | Page Up, Page Down | Moves the thumb by a larger step. |
+   * | Page Up, Page Down | Moves the thumb by `page-step`, or by the platform's larger step where it is not set. |
    * | Home, End | Moves the thumb to its lowest or highest value. |
    *
    * Under `readonly` none of these move the thumb, and Tab still reaches it.
@@ -84608,6 +85078,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
@@ -84840,6 +85313,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.
    */
@@ -88021,20 +88496,25 @@ export type CustomElementsSolidJs = {
    * `seconds`, because that is what the form
    * submits, what `min` and `max` compare against, and what sorts correctly as a
    * string. While idle, the field shows the time in the user's locale format.
-   * Once the caret is in the field, it shows the value itself, because a
-   * formatted time such as `2:30 PM` cannot be typed back and `Intl` has no
-   * parser for it.
+   * Once the caret is in the field, it shows the value itself. You can type
+   * `14:30`, or a time as you write one, such as `2:30 PM`, `2.30pm`, or
+   * `14h30`, and the field reads it as you leave it, with AM and PM in the
+   * locale's words.
    *
    * Typing sends `input` on each keystroke and `change` when you leave the
    * field. The trigger and ArrowDown open the list, and so does a press into the
-   * field; Tab into the field opens nothing. In the list, the arrow keys, typed digits and PageUp and PageDown
+   * field; Tab into the field opens nothing. The text field is a `combobox`
+   * with `aria-haspopup="dialog"`, `aria-expanded`, and `aria-controls`, since
+   * Down opens the list from it. In the list, the arrow keys, typed digits and PageUp and PageDown
    * move through the times, and Enter, Space or a click chooses one and closes
    * the panel. With `variant="wheels"` each wheel moves the time as you turn it,
    * the panel stays open, and Enter or Escape closes it.
    *
    * With `segmented`, the field is a row of segments in place of the text: an
    * hour, a minute, and AM or PM where the clock has them, each set with digits
-   * or the arrow keys. Alt+Down opens the list from a segment.
+   * or the arrow keys. Alt+Down opens the list from a segment. A `range` is two
+   * rows with a dash between them, the start and the end, and `multiple` keeps
+   * the text.
    *
    * Text that is not a time gives the form an empty value, as a native time
    * field does, and `value` keeps the text so it can be corrected.
@@ -88066,6 +88546,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
@@ -88114,6 +88598,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.
    *
@@ -88136,6 +88622,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.
    *
@@ -88287,6 +88777,7 @@ 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.
    * - `toggle`: Fired after the list opens or closes, with `newState` and `oldState`.
    *
@@ -88294,6 +88785,7 @@ export type CustomElementsSolidJs = {
    *
    * 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.
@@ -88367,6 +88859,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.
@@ -88412,6 +88905,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`.
@@ -88432,6 +88926,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.
@@ -88488,7 +88983,10 @@ export type CustomElementsSolidJs = {
    * host's `aria-label` or its `aria-labelledby`. A development build warns
    * where all four are empty. The list is described by the hint, or by the
    * message in `feedback` in its place, and carries `aria-multiselectable` with
-   * a `mode` and `aria-invalid` while `feedback` says what is wrong. The wheels
+   * a `mode`. It carries `aria-invalid` while `feedback` says what is wrong,
+   * while it holds a time outside `min` and `max` or one the picker does not
+   * offer, and, for a `required` picker with no time, once the reader has
+   * chosen one or a form has refused the picker. The wheels
    * are a `group` with that name, holding one `listbox` per wheel, named "Hour",
    * "Minute", "Second" and "AM/PM" in the page's language, and each described
    * the same way.
@@ -88846,7 +89344,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.
@@ -88860,7 +89358,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-headless-time-picker": Partial<
@@ -89456,7 +89955,7 @@ export type CustomElementsSolidJs = {
    * | Right, Down | Moves to the next item, from the last back to the first. In a single group, chooses it. |
    * | Left, Up | Moves to the item before, from the first round to the last. In a single group, chooses it. |
    * | Home, End | Moves to the first or the last item. In a single group, chooses it. |
-   * | Space, Enter | Chooses the focused item, or presses or releases it in a multiple group. |
+   * | Space, Enter | Chooses the focused item, or presses or releases it in a multiple group. With `allow-empty-selection`, takes back the chosen item. |
    *
    * Left and Right swap on a right-to-left page, and a disabled item is passed
    * over. A single group is a `radiogroup` of items with `role="radio"` and
@@ -89468,6 +89967,11 @@ export type CustomElementsSolidJs = {
    *
    * Component attributes and properties that can be applied to the element or by using JavaScript.
    *
+   * - `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
@@ -89813,13 +90317,13 @@ export type CustomElementsSolidJs = {
    *
    * Custom selectors for styling elements within the component.
    *
-   * - `item`: The radio button.
+   * - `item`: The button: a radio in a group where one is chosen, and a button with `aria-pressed` on its own or in a group where several can be.
    *
    * ## CSS States
    *
    * 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.
    */