Skip to content

An open source design system that's fully customizable and agent ready

TypeScript
59.0 KB
Raw Blame

schema_version: 3 template_version: 7 kind: component id: component:DateTimeInput authority: current archive_reason: null superseded_by: null approved_by: cixzhang approved_at: 2026-10-30 owners: [cixzhang] review_triggers: [public-api, behavior, layout, theming, accessibility] verified_by: [ packages/core/src/DateTimeInput/DateTimeInput.test.tsx, packages/core/src/DateInput/TouchDateToday.ssr.test.tsx, packages/core/src/DateTimeInput/DateTimeInputTouch.test.tsx, packages/core/src/DateTimeInput/NativePickerSegments.test.tsx, packages/core/src/DateTimeInput/Presentation.test.tsx, packages/core/src/DateTimeInput/DateTimeInput.fr10.test.tsx, packages/core/src/DateTimeInput/DateTimeInput.calendar.test.tsx, packages/core/src/DateInput/DateInput.calendarPresentation.test.tsx, packages/core/src/DateInput/DateInputTouch.calendar.test.tsx, packages/core/src/DateInput/DateInput.noTemporal.test.tsx, packages/core/src/tests/BusyOwnerAnnouncement.test.tsx, packages/core/src/theme/themingTargets.test.ts, scripts/check-knowledge.mjs, ] modules: [] families: [family:input-fields, family:overlay-dismissal] design_specs: [] architecture: [ architecture:component-theming-surface, architecture:internationalization, architecture:public-component-api, ] contributing: [] system_specs: [ spec:AST-013/FR9, spec:AST-013/FR12, spec:AST-043, spec:AST-085, spec:AST-086, spec:AST-102, spec:AST-111,

]

DateTimeInput component contract

Contract at a glance

Area Contract
Public contract One controlled ISO date-time value presented through coordinated date and time segments; presentation selects Astryx, native, or adaptive picker surfaces. calendar selects the calendar system the date segment shows on every surface (spec:AST-111 FR2).
Behavior Date and time changes emit one combined value; clear emits undefined; controlled empty state remains empty in every rendered picker. The pointer date segment reads and writes typed dates in the resolved calendar and reports a typed date only when it is complete (FR11). With a calendar other than gregory or iso8601, a presentation that would show native controls shows the popovers on a fine pointer and the bottom sheet on a coarse pointer, and the bottom sheet shows months of the calendar (FR12).
End-user impact People selecting a date and time see one value reflected consistently in the closed field and the active picker, including after clearing.
Builder impact A caller that relied on the 12h hour-format default under a 24-hour locale passes hourFormat="12h" to keep twelve-hour time text. A per-user 12/24-hour preference goes on the provider locale as a -u-hc- extension (en-US-u-hc-h23).
Compatibility/readiness The hourFormat default is the provider locale's hour cycle (12h for en/en-US and with no provider); every other released default, API, and DOM shape holds. The presentation matrix and deprecated nativePicker mapping follow spec:AST-043. Fixed segment height, typed-time prefix commits, busy paint, and caller handlers while disabled are listed under Current-state impact. calendar is additive with a Gregorian default; typed Gregorian dates follow FR11, and calendars that need Temporal fall back to Gregorian where it is missing (the spec:AST-013 FR12 exception).
Review checks Reject competing picker selection, date/time output that is not one valid combined value, presentation precedence drift, lost per-segment fallback, or broken segment accessibility.
Governing rules spec:AST-043, family:input-fields, family:overlay-dismissal, spec:AST-085, spec:AST-086 FR8, spec:AST-111 FR2, FR3, FR9–FR16, AR2, AR3, spec:AST-013 FR12, and objective platform accessibility standards.

This table is a review projection; the body below is authoritative.

Intent

DateTimeInput presents one controlled date-time value as coordinated date and time segments under one field label. Depending on presentation, the segments use Astryx popovers, one coordinated bottom sheet, browser or operating-system inputs, or pointer-adaptive combinations of those surfaces.

Compatibility and migration

  • Released default preserved: yes, except hourFormat, which follows the provider locale's hour cycle (12h for en and en-US, the released default with no provider) and shares TimeInput's locale time text
  • Compatibility class: default change for non-English-US locales; additive calendar prop with a Gregorian default; typed Gregorian dates fire onChange only for complete input (FR11); a non-Gregorian calendar replaces native controls with the Astryx surfaces for the pointer, and an explicit native warns in development (FR12); existing types, callbacks, roles, and exports remain stable. A provider locale with a -u-ca- keyword keeps Gregorian dates (spec:AST-111 DEC-2); set calendar to choose one.
  • Controlled/uncontrolled behavior: DateTimeInput remains controlled; undefined represents no committed date-time value
  • Migration decision: none; picker presentation and deprecated nativePicker compatibility remain governed by spec:AST-043

Consumer migration instructions belong in consumer docs and release notes.

Ownership boundary

Owns

  • Coordinating date and time segments into one controlled ISO date-time value.
  • Choosing and composing the date and time surfaces selected by presentation.
  • Applying component-local date-time bounds, date constraints, time precision, typed-time stepping, and optional preset-time behavior.
  • Emitting onChange before an optional optimistic changeAction.
  • The disabled-reason Tooltip composition, which family:input-fields assigns to the member.

Does not own / non-goals

  • Field label, description, status, and clear-button presentation — owned by Field under family:input-fields (shared owner section) and component:FieldStatus.
  • Calendar-grid rendering and date-cell interaction — owned by Calendar.
  • Popover and sheet hosting or dismissal — owned by the composed layer components and family:overlay-dismissal.
  • The sheet wheels' rest, motion, scroll input, and look — owned by component:DateInput (FR13–FR15, DEC-1, DEC-2).
  • Cross-component picker-presentation vocabulary and deprecated-prop mapping — owned by spec:AST-043.

Public concepts

Concept Closed values or states Meaning Availability by variant/orientation/state Default Owner Stability Invalid-value behavior
Committed date-time valid ISO local date-time string or undefined The one controlled value reflected by both segments and active picker. Every presentation. undefined component:DateTimeInput Stable Unreadable text reverts; a date the calendar lacks, out of range, or incomplete stays for correction; neither emits change.
Picker presentation popover, bottom-sheet, native, adaptive-bottom-sheet, adaptive-native Selects which surface collects date and time. Every render; pointer adaptation applies only to adaptive values. adaptive-native spec:AST-043 Stable Type-rejected.
Legacy picker selection touch, always, never Deprecated compatibility input mapped by spec:AST-043; presentation wins. When presentation is omitted. touch spec:AST-043 Deprecated Type-rejected.
Time precision minute-only or seconds Controls value precision and whether native time can represent it. Every presentation; native fallback follows spec:AST-043. minute-only component:DateTimeInput Stable Type-rejected.
Preset-time cadence omitted, 5, 10, 15, 30, or 60 minutes Adds a fine-pointer time listbox without restricting typed entry. Astryx pointer time field only. omitted component:DateTimeInput Stable Type-rejected.
Calendar a CalendarSystem (spec:AST-111 FR1) The calendar system the date segment shows dates in. Every surface; a calendar other than gregory or iso8601 replaces native controls (FR12). the provider's resolved calendar, else gregory (spec:AST-111 FR2) spec:AST-111 stable Resolves to gregory and warns once in development; a calendar that needs Temporal falls back to gregory where it is missing.

Behavioral and layout contract

ID Invariant Basis
FR1 DateTimeInput MUST reflect one controlled date-time value across its visible segments and active picker, and MUST NOT reveal a competing selected date after the parent accepts a clear. Public docs, controlled component seam, current source, focused tests
FR2 Every committed date or time change MUST emit one valid combined ISO date-time value; clearing MUST emit undefined; changing time while no date is committed MUST emit nothing. Public types, docs, current source, focused tests
FR3 presentation, deprecated nativePicker, precedence, pointer adaptation, forced surfaces, and per-segment native fallbacks MUST follow spec:AST-043 FR1–FR4, except that a calendar other than gregory or iso8601 replaces native surfaces as FR12 states. The touch date sheet's month heading and month-pane names follow component:DateInput FR6, and its weekday row follows component:DateInput FR19. spec:AST-043
FR4 When changeAction is present, every value-change path MUST call onChange first, show the proposed controlled value optimistically, and contribute to one busy state until the controlled value accepts or replaces it. family:input-fields/FR6
FR5 The two pointer segments share one row while each retains its intrinsic basis; when the container is narrower, flex wrapping moves them into separate full-width rows. Each segment is the shared element height for its size, as a minimum that grows with a set text size under spec:AST-102 FR4. Implementation gap: the height is fixed at that size. Public docs, current source, focused layout tests; spec:AST-102 FR4
FR6 Date-time bounds and date constraints MUST prevent invalid commits. Native controls MAY receive platform hints, but JavaScript validation remains the final commit boundary; calendar-only options MAY be unavailable on native surfaces. Public docs, current source, focused presentation tests
FR7 A preset-time listbox MUST remain optional, preserve typed entry, expose one selected option independently from keyboard highlight, and limit offered values to the selected date's effective minimum and maximum. Time text and typed times MUST follow the active locale's digits, separator, and day-period words (architecture:internationalization INV1a, INV8). The hour format is hourFormat when set, else the provider locale's hour cycle; time text, preset options, and the stepped-time announcement come from the shared time formatter, and typed times parse the locale's digits, separators, and day-period words as well as English. Implementation gap: the typed time field commits as soon as a prefix parses. While open, the listbox stays open for a press on the time field or in the listbox and closes for a press elsewhere (architecture:layer-runtime). Public docs, current source, focused interaction tests; architecture:internationalization INV1a, INV8
FR8 Base props and ref MUST reach the date segment's input; a caller aria-describedby joins the component's own descriptions, and a caller DOM handler runs after the field's own handler. container* reaches the Field box and control* the segment row; root xstyle, className, and style are not accepted. family:input-fields FR10; DateTimeInput.fr10.test.tsx
FR9 A disabled field MUST keep both segments focusable with aria-disabled and no native disabled, block every value-changing path, keep the calendar button's tab stop, and paint the keyboard focus ring. Explicit isLoading makes every surface inert the same way; a pending changeAction does so only on the popover surface, and the bottom sheet and any field with a native date segment keep accepting edits. The busy start is announced once. Implementation gap: a caller onKeyDown and other DOM handlers on the date segment still run while disabled (spec:AST-085 FR2). Implementation gap: a busy field that is not disabled takes the disabled paint (half opacity), on every surface while isLoading and on the popover while a changeAction is pending, against spec:AST-085 FR6. spec:AST-085 FR1, FR2, FR6; spec:AST-086 FR8; current source and tests
FR10 Enter in the date segment's text input commits typed text that has not been committed and is then held back, so a form never submits the value from before the commit. With no typed text pending, Enter is not prevented, so a form submits as it does from any text field, except on a disabled or busy field, where Enter does nothing (spec:AST-085 FR2).
FR11 The pointer date segment follows component:DateInput FR20 for typed entry in the resolved calendar: it reads the dates Intl.DateTimeFormat writes for the locale and calendar, and in the Gregorian calendar, on Enter or blur, text it cannot otherwise read and a date the locale's field order lacks, such as 13/5/2026 in en-US, when parseDateInput reads it, with a one- or three-digit year not a date, reads years of the calendar, rejects a date the calendar does not have without adjusting it, shows and announces an out-of-range error with the bounds in the calendar, fires onChange while typing only for complete input and at most once for each distinct date in one typing session, shows and announces each rejection once as DateInput does, and writes the committed date as date_long in the calendar (spec:AST-111 FR9–FR13). Its Calendar shows the same calendar, and the combined value stays a Gregorian ISO date-time (spec:AST-111 FR3). spec:AST-111 FR3, FR9–FR13; current source; calendar typed-entry tests
FR12 With a calendar other than gregory or iso8601, every presentation that would show native controls — adaptive-native, the default, deprecated touch and always, and an explicit native — shows the Astryx popovers on a fine pointer and the bottom sheet on a coarse pointer, for the date and the time alike, because the native date control is Gregorian (spec:AST-111 FR15). An explicit native also warns once in development. The bottom sheet's Date panel follows component:DateInput FR21: calendar months in six-row panes, the month wheel of the selected calendar year with leap months, the common counterpart on a year change, and year labels with their era; its date segment writes the date as date_long in the calendar (spec:AST-111 FR16). The combined value stays a Gregorian ISO date-time (spec:AST-111 FR3). spec:AST-111 FR3, FR15, FR16; current source; calendar presentation and touch calendar tests
FR13 While disabled or busy, the date segment keeps or drops typed text as component:DateInput FR12 states, judging it on the next Enter or blur once editable. spec:AST-085 FR2; current source and tests
FR14 Under a coarse primary pointer, the date sheet's month and year wheels MUST move a chosen date as component:DateInput FR23 does, keeping its time. component:DateInput FR23; UIDatePicker on the iOS 26.2 simulator

Allowed variation

  • AV1 — Surface. The caller may force Astryx, native, or bottom-sheet surfaces, or choose an adaptive presentation within the current system-spec matrix.
  • AV2 — Date and time formatting. Locale, hour format, seconds, week start, month count, and preset cadence may vary through their documented inputs.
  • AV3 — Optional field support. Clear, loading, status, disabled reason, description, and label visibility may be omitted without changing value ownership.

Representative states

State Required invariant Allowed variation
Empty Both segments and every active picker expose no committed selection. Placeholder and selected surface.
Date-time value Date segment, time segment, and active picker reflect the same committed value. Locale, hour format, and time precision.
Cleared after picker change Closed field is empty and reopening the picker reveals no selected date or retained committed time. Picker focus date may remain navigational.
Busy Proposed value remains visible; both editable segments expose busy. With explicit isLoading, mutation paths are unavailable on every surface; with a pending changeAction, only on the popover surface. Explicit loading or pending action source.
Focusable disabled Both segments stay focusable with aria-disabled while every value-changing path stays blocked. Disabled-reason text.
Calendar Every surface shows the resolved calendar, and native controls give way to the popovers or bottom sheet outside gregory and iso8601; the value stays Gregorian ISO. Calendar, locale, digits

Transformation and precedence order

  • ORD1 — Picker selection. Resolve presentation before deprecated nativePicker; with a calendar other than gregory or iso8601, use adaptive-bottom-sheet in place of native and adaptive-native (FR12); apply pointer adaptation, then apply only the per-segment native fallbacks permitted by spec:AST-043.
  • ORD2 — Value mutation. Validate the proposed segment value, combine it with its committed counterpart, call onChange, present the optimistic combined value, then run changeAction in a transition.

Performance and resources

  • PR1 — Preset options. The time listbox mounts option nodes only while open; omitted preset cadence leaves no listbox nodes or combobox semantics.

Current measurements belong in the audit record; this subsection owns only durable constraints and their verification target.

Accessibility contract

  • AR1 — Field naming. The date segment is named by the field label; the time segment uses timeLabel or a localized label-derived fallback. Description, status, and disabled-reason text remain referenced from both segments.
  • AR2 — Picker semantics. The Astryx date segment is a combobox controlling a dialog; the optional preset-time field is a combobox controlling one listbox. Omitted preset cadence leaves the time field without combobox semantics.
  • AR3 — Keyboard and focus. Documented keyboard activation, date-popover dismissal, preset-time navigation, focus containment, and focus restoration remain operable on their active surfaces.
  • AR4 — Required, invalid, busy, and disabled. Both editable segments expose applicable required, invalid, busy, and disabled states; a focusable disabled reason never re-enables mutation.
  • AR5 — Typed-date rejections and the calendar. Unreadable text, a date the calendar does not have, and an out-of-range date each announce a different catalog message from the date segment, and the last two also show it as the field's error status, in place of a caller status while the rejected text stays (spec:AST-111 AR3). The pointer date segment's description names the calendar only when its resolved calendar differs from the provider's resolved calendar, else gregory, with gregory and iso8601 as one calendar, both compared after the Gregorian fallback for a runtime without Temporal. With a calendar other than gregory or iso8601 and no caller placeholder, the empty focused segment shows an example date in the calendar's numeric pattern; a caller placeholder shows in every state and replaces the hint. The example date is today when the field accepts it, else the nearest date it accepts (spec:AST-111 AR2).

Design relationships

Anatomy or state Design requirement Representation authority Hierarchy role Component contract
Segment row Groups the two bordered segments and wraps them as one layout row. Current source and public docs Prominent FR1, FR5
Date segment Presents date text and access to the active date picker. Current source and public docs Prominent FR1–FR3, AR1–AR3
Time segment Presents time text and access to the active time surface. Current source and public docs Prominent FR1–FR3, AR1–AR3
Picker surfaces Collect date and time without becoming competing values. spec:AST-043 and composed component contracts Supporting FR1–FR3
Busy/disabled/status Uses shared input-family representations. family:input-fields Supporting FR4, AR4

The component implements design requirements without copying their rationale. An unsettled representation remains a human decision; principles do not let an agent invent the answer.

Theming anatomy

{
  "Label": {
    "delegatesTo": {"owner": "component:Field", "target": "field-label"}
  },
  "Segment row": {"target": "date-time-input"},
  "Date input": {"target": "date-time-input-date-segment"},
  "Calendar icon": {"target": "date-time-input-toggle-icon"},
  "Date picker": {
    "none": {
      "reason": "reachability-gap: Active picker paint is owned by Calendar, Popover, BottomSheet, or the browser-native control, so no single DateTimeInput target reaches every presentation."
    }
  },
  "Time input": {"target": "date-time-input-time-segment"},
  "Clock icon": {"target": "date-time-input-clock-icon"},
  "Time options popover": {"target": "date-time-input-time-listbox"},
  "Time option": {"target": "date-time-input-time-option"},
  "Clear button": {
    "delegatesTo": {"owner": "component:Field", "target": "input-clear-button"}
  },
  "Status message": {
    "delegatesTo": {"owner": "component:FieldStatus", "target": "field-status"}
  }
}

The calendar-toggle target reflects expanded or collapsed state. The time-options listbox owns option rows through the date-time-input-time-option target; the leading clock glyph uses date-time-input-clock-icon.

Family and system relationships

  • family:input-fields owns shared field sizing, end-control geometry, loading, optimistic change actions, status placement, disabled reasons, and iOS text-entry focus-zoom behavior.
  • family:overlay-dismissal owns the Popover and BottomSheet dismissal stack.
  • architecture:component-theming-surface owns target admission, state reflection, and anatomy mapping.
  • spec:AST-043 owns picker-presentation values, defaults, precedence, compatibility mapping, forced surfaces, and native fallback rules.
  • spec:AST-111 owns calendar selection, Gregorian ISO values, the Temporal boundary, typed entry, and presentations in a calendar; FR11, FR12, and AR5 project its FR3, FR9–FR13, FR15, FR16, AR2, and AR3 through component:DateInput FR20 and FR21.

spec:AST-013 FR12 exception — calendars that need Temporal

  • Capability: typed date entry, committed date text, and the bottom sheet's Date panel in calendars other than gregory, iso8601, buddhist, roc, and japanese, which need the runtime's Temporal.
  • Reduction: where Temporal is missing, as in Safari on macOS and iOS, the date segment reads, writes, and shows Gregorian dates, its presentations resolve as they do for gregory, and it warns once in development, naming a polyfill (spec:AST-111 FR5). An application that loads a Temporal polyfill gets the full calendar. When a server and a browser use chinese or dangi implementations that disagree on a month start, React renders the differing text again on the client (spec:AST-111 FR19).
  • Preserved obligations: spec:AST-013 FR7 and FR8, and FR9 outside that chinese and dangi case. The Gregorian date and time segments keep every interaction, label, and announcement, and Buddhist, Minguo, and Japanese entry works without Temporal.
  • Evidence: real Chromium and Firefox typing in calendar fields with native Temporal, with Temporal removed and a polyfill loaded, and with Temporal removed and no polyfill, through the shared DateInput field; the shared bottom sheet in real Chromium, Firefox, and WebKit in the same three modes.
  • Owner: nynexman4464.
  • Review condition: Safari ships Temporal.

Verification map

Contract Verification Representative states Mutation or failure expectation Audit section
FR1–FR2 DateTimeInput.test.tsx empty, calendar selection, typed date/time, clear A stale Calendar selection, partial output, or invalid mutation makes a public-state test fail. audit:DateTimeInput/behavior
FR3, FR6 Presentation.test.tsx, NativePickerSegments.test.tsx, DateTimeInputTouch.test.tsx (including "labels the date sheet columns in %s with the Calendar header names" for en-US, pt-PT, and id-ID) forced, adaptive, legacy, native fallback, constrained commit A substituted surface, precedence drift, or invalid commit makes a presentation test fail. audit:DateTimeInput/surfaces
FR4, FR9, AR4 DateTimeInput.test.tsx, DateTimeInputTouch.test.tsx; BusyOwnerAnnouncement.test.tsx DateTimeInput case pending, loading, disabled reason Mutation during busy/disabled state or stale optimistic output makes a state test fail. Evidence gap: no test asserts that caller handlers still run while disabled. audit:DateTimeInput/state
FR5 DateTimeInput.test.tsx intrinsic row, narrow-container wrap classes Removing the intrinsic basis or wrap styles makes the class-level layout assertions fail; rendered geometry remains review evidence. Evidence gap: no test asserts segment heights or text growth. audit:DateTimeInput/layout
FR7, AR1–AR3 DateTimeInput.test.tsx, DateTimeInputTouch.test.tsx; DateTimeInput.test.tsx "keeps the time list open on a press in the time input, closes it on a press elsewhere" popovers, time options, keyboard/focus Wrong role, name, state, keyboard behavior, or focus behavior makes a focused interaction test fail. A provider-locale test asserts the closed time text follows the locale's hour cycle and day period; the shared formatter's tests cover parsing. audit:DateTimeInput/interaction
FR8 DateTimeInput.fr10.test.tsx each surface; caller id, describedby, onClick, onKeyDown A base prop off the date input, a dropped caller description, or styling on the wrong part fails. audit:DateTimeInput/api
FR10 DateTimeInput.test.tsx "Enter in the date segment submits the form when nothing is typed, and commits typed text without submitting" "Enter on a disabled field does not submit the form" and "Enter on a busy field does not submit the form" Nothing typed; typed text; disabled; busy (isLoading) An Enter that is prevented with nothing typed, or that submits before typed text commits, fails. —
FR11, AR5 DateTimeInput.calendar.test.tsx ("reports one Persian date typed in Persian digits, only when complete", "writes the committed date in the calendar", "rejects a date the calendar does not have and names the calendar", "shows an out-of-range error with the bounds in the calendar", "names the calendar and shows the hint when focused and empty", "shows a caller placeholder instead of the format hint", "names no calendar when the field uses the provider calendar", "names the Gregorian calendar inside a Persian provider", "commits Gregorian text that only parseDateInput reads on blur", "commits a day-first date that does not exist month-first, on blur only", "fires once for a day-first Gregorian date typed one key at a time"); the parser and round-trip suites under component:DateInput FR20 Persian digits, Hebrew leap year, Japanese era bound, Gregorian day-first typing A typed date reported before it is complete, an adjusted date, a shared rejection message, a hint that replaces a caller placeholder, a calendar description that is missing or that repeats the provider's calendar, or a non-ISO value fails. Evidence gap: no real-browser run drives the DateTimeInput date segment itself. audit:DateTimeInput/behavior
FR12 DateInput.calendarPresentation.test.tsx DateTimeInput cases (every presentation and deprecated nativePicker value in Gregorian and Persian on fine and coarse pointers; "warns once when an explicit native cannot show the calendar"; "writes the sheet date segment in %s %s with its era" for en and fa-IR Persian and th-TH Buddhist); DateInputTouch.calendar.test.tsx "shows Persian months and the date in the calendar"; DateInput.noTemporal.test.tsx "shows a Persian DateTimeInput as Gregorian native controls" Persian on fine and coarse pointers, explicit native, no Temporal A native date or time control for a non-Gregorian calendar, a missing warning for an explicit native, or a Date panel in another calendar, fails audit:DateTimeInput/surfaces
FR13 DateTimeInput.test.tsx "typed text while the field is disabled or busy" cases Loading, disabled, and saves; unfinished, valid, reported, rejected, new value A commit, onChange, reset, or rejection while disabled or busy, a rejection that does not return once editable, typed text that outlives a new value, or reported text that outlives the lock fails. audit:DateTimeInput/state
FR14 DateTimeInputTouch.test.tsx "under a finger: moves the chosen date with the month wheel, keeping the day and the time", "under a finger: a date the month wheel moves runs changeAction after onChange, shows at once, and is busy until it settles (family:input-fields FR6)", "under a finger: opening the month/year wheels on a date outside the range changes nothing", "under a finger: keeps a date a custom constraint refuses, while the calendar moves" A month turn with a time; a pending Action; opened out of range; a refused date A wheel that drops the time, leaves the date behind, changes the value on opening, or chooses a refused date fails. audit:DateTimeInput/surfaces
Theming anatomy map scripts/check-knowledge.mjs, themingTargets.test.ts root, segments, icons, listbox, options Missing, undocumented, or wrongly placed targets fail knowledge or target checks. audit:DateTimeInput/theming

Current-state impact

  • Fixed height (FR5). Segments hold the fixed shared element height instead of growing with a set text size, against spec:AST-102 FR4.
  • Typed-time prefix commits (FR7). The typed time field commits a parsed prefix, so a typed time can commit a different time, against architecture:internationalization INV8.
  • Busy paint (FR9). A busy field that is not disabled takes the disabled half-opacity paint, against spec:AST-085 FR6.
  • Caller handlers while disabled (FR9). Caller DOM handlers on the date segment, such as onKeyDown, still run while disabled, against spec:AST-085 FR2.

Decision log

No component-local decision. Cross-component picker decisions live in spec:AST-043.

Open questions

None.

Content boundary

This file does not duplicate consumer prop tables or examples, current audit results, implementation steps, Calendar/Field/layer contracts, or the picker-presentation system specification.