Tracking issue for integration into the web platform

[ptomato]

• Integration with structuredClone: Temporal proposal HTML serialization support whatwg/html#6284
• Integration with <input type="date"> etc.: integration with <input type="time"> and <input type="date"> #107, valueAsTemporal: date/time input integration with JavaScript Temporal API whatwg/html#10882
• IDL conversion from Temporal.Instant/ZonedDateTime to DOMHighResTimeStamp (as described in Cookie expiration time could take Temporal.Instant or Temporal.ZonedDateTime in addition to DOMHighResTimeStamp whatwg/cookiestore#243 (comment))
• (Currently nonexistent) duration input element: <input type="time"> : Time vs. duration whatwg/html#5488

[TheOneTheOnlyJJ]

whatwg/html#3281 and whatwg/html#5475 could also be added here, the same way as whatwg/html#5488 is mentioned.
Both are related to and could be integrated with Temporal.

whatwg/html#5475 would depend on js-temporal/proposal-temporal-v2#4, which may be out of the scope of this issue. If it is considered so, it could be referenced there instead.

Update: Adding nodejs/node#57891 here.

[ptomato]

Thanks for the suggestions. We have a different tracking issue for integration with Node (and since it was opened, other server runtimes) and I've added that link there: #141

<input type="year"> is not something that could integrate with Temporal as currently proposed — we don't have a data type that represents a bare year.

[ptomato]

Ideas from the Web Engines Hackfest 2025

• setTimeout, AbortSignal.timeout, and friends taking a Temporal.Duration
• alarms
• (in ECMAScript!) Atomics.wait timeout argument