Re: [w3ctag/design-reviews] Temporal proposal (#311)

> Has TC39 thought about `HTMLTimeElement` integration? Or how this can work with `<input type="time">`?

Our `CivilTime` object should map nicely to `<input type="time">`.  Likewise, our `CivilDate` object should map nicely to `<input type="date">` in a way that the current `Date` object does not.

I previously hadn't looked much at `HTMLTimeElement`, but on cursory scan, not every data type listed there would have a distinct object in Temporal - at least not with the initial implementation.  Using the terminology listed there:

- ❌ Valid month string
- ✔️ Valid date string  (Temporal `CivilDate`)
- ❌ Valid yearless date string
- ✔️ Valid time string  (Temporal `CivilTime`)
- ✔️ Valid local date and time string  (Temporal `CivilDateTime`)
- ❌ Valid time-zone offset string
- ✔️ Valid global date and time string  (Temporal `ZonedInstant`)
- ❌ Valid week string
- ❌ Four or more ASCII digits
- ❌ Valid duration string


-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/311#issuecomment-434843730