Live preview
What you try is exactly what we testedDemo
Live demo: DateTimeInput
What you try is exactly what we testedWhat it is
An input for date and/or time.
In the trip planner
The trip planner does not use DateTimeInput. The settings form in the same explorer shows it in use. Open the explorer.
Properties
| Property | Type | Required | Allowed values | New in 1.0 |
|---|---|---|---|---|
value | DynamicString | yes | – | |
enableDate | boolean | no | – | |
enableTime | boolean | no | – | |
min | unspecified | no | – | |
max | unspecified | no | – | |
label | DynamicString | no | – |
Evidence
PASS React 0.15.0 with web_core 0.15.0, v1.0 module · headless Chromium, Linux · 2026-11-14 · 1 run
What is not claimed
- Other renderers (Lit, Angular, community) were not rerun; the 8 November 2026 matrix stands.
- Gemini Enterprise was not tested in this run (14 November 2026).
- Remote media was not loaded, so media records element creation and attributes, not playback.
- Layout and visual quality are not judged.
Media and links in the examples use example.invalid placeholders. Navigation is intercepted and media is not played.
Findings
Findings
- The value is written as ISO 8601 without a timezone offset (for example 2026-12-25T10:30:00). Our Express prompt asks for RFC 3339 with an offset: to reconcile.
- In React 0.15.0 the date input has no label (axe rule "label"). Still unlabelled on the project's main branch, unreleased (checked 14 Nov 2026 at commit 3ed960186).
Recorded cases
| Case | Expected | Observed | Verdict |
|---|---|---|---|
date input change -> model string | date input writes a date string | PASS | |
enableDate+enableTime change -> model string format | value is an ISO 8601 string | observed 2026-12-25T10:30:00 (no timezone offset); the catalog says ISO 8601, while the Express prompt asks for RFC 3339 with an offset | OBSERVED |
time only change -> model string format | time input writes a time string | PASS |