You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This GitHub issue is for collecting web developer signals for Temporal.
The Temporal API allows you to work with dates, times, time zones, and durations. It is more powerful than the Date API.
Browser support
Chrome 144 (Jan 13, 2026)
Chrome Android 144 (Jan 13, 2026)
Edge 144 (Jan 21, 2026)
Firefox 139 (May 27, 2025)
Firefox for Android 139 (May 27, 2025)
Safari: not supported
Safari on iOS: not supported
Give us feedback
If you're pressed for time, but you want this feature to be available in all browsers, please give this issue a thumbs up 👍 reaction.
However, a much better guide for us is to know how you'd use this feature, and what you're having to do in the meantime. This helps us judge the priority versus other features.
Copy the template below in a comment, and add the details that matter to you.
## What I want to do with this feature<!-- Add your specific use-cases, even if they seem obvious to you. -->## What I'm having to do in the meantime<!--Are you having to use another feature instead, a polyfill, or is it blocking you completely?Why are the alternatives worse than using this feature?-->
I want to handle partial date and time data (only time or only day, or dates without timezone).
What I'm having to do in the meantime
In the meantime I use JavaScript Date objects to represent such data, but I have to be careful to set the value of unused fields for comparisons to work as expected (forgetting to do so can lead to unexpected problems).
Reacted by Jake Archibald, Oskar Larsson Högfeldt, Christian Røen, Peter, Matthew W, Dmitrii Baranov, ittixen and Axel Havukangas
Easily handle dates, times, months (with years but not dates) in a straightforward manner, without writing string parsers and normaliser functions. The localisation support and timezone handling is an added bonus.
What I'm having to do in the meantime
I have to use a polyfill if there's any chance my users use iOS or Safari.
Let's see I am using temporal for zdt (ZonedDateTime) and IANA time zone names and time zone support in ways that Date() never could
I'm using temporal inside an astronomical/celestial app with topographic observer corrections, so strong local time zone support is very much a hard requirement.
What I'm having to do in the meantime
BTW, this just doesn't work on iOS right now, and I have no intention of backfilling or polyfilling or anything else.
@anthonymhumphreys I took the liberty to apply the template to your comment. I did not change the content of your comment, I only added the headings from the template. Thank you for your comment.
I work on an app used by folks across the country with a lot of client-set dates and datetimes. These date(time)s have no need to be timezone-aware, so using Temporal (without introducing a polyfill) will allow us to simplify all of our date handling and remove dependencies.
Workarounds currently used
Use date-fns/date-fns-tz for date manipulation and timezone handling (despite formatting all going through Intl.DateTimeFormat). We also have our own robust suite of helpers to ensure timezones are displayed consistently regardless of server/client drift.
I want to represent dates without time or time zone information attached.
What I'm having to do in the meantime
I'm using a mix of custom { year: number; month: number; day: number; } objects and YYYY-mm-dd strings, and need some custom functions for checking if a date in this representation aligns with the current day based on the user's time zone.
Activity
PotatoesMaster commentedon Dec 11, 2025
What I want to do with this feature
I want to handle partial date and time data (only time or only day, or dates without timezone).
What I'm having to do in the meantime
In the meantime I use JavaScript Date objects to represent such data, but I have to be careful to set the value of unused fields for comparisons to work as expected (forgetting to do so can lead to unexpected problems).
DNSCond commentedon Jun 5, 2026
What I want to do with this feature
What I'm having to do in the meantime
im using a polyfill and some overflow code to achive what i want.
darovic commentedon Jun 6, 2026
What I want to do with this feature
Easily handle dates, times, months (with years but not dates) in a straightforward manner, without writing string parsers and normaliser functions. The localisation support and timezone handling is an added bonus.
What I'm having to do in the meantime
I have to use a polyfill if there's any chance my users use iOS or Safari.
anthonymhumphreys commentedon Aug 10, 2026
What I want to do with this feature
Let's see I am using temporal for zdt (ZonedDateTime) and IANA time zone names and time zone support in ways that Date() never could
I'm using temporal inside an astronomical/celestial app with topographic observer corrections, so strong local time zone support is very much a hard requirement.
What I'm having to do in the meantime
BTW, this just doesn't work on iOS right now, and I have no intention of backfilling or polyfilling or anything else.
captainbrosset commentedon Aug 11, 2026
@anthonymhumphreys I took the liberty to apply the template to your comment. I did not change the content of your comment, I only added the headings from the template. Thank you for your comment.
lowmess commentedon Sep 11, 2026
What I want to do with this feature
I work on an app used by folks across the country with a lot of client-set dates and datetimes. These date(time)s have no need to be timezone-aware, so using Temporal (without introducing a polyfill) will allow us to simplify all of our date handling and remove dependencies.
Workarounds currently used
Use
date-fns/date-fns-tzfor date manipulation and timezone handling (despite formatting all going throughIntl.DateTimeFormat). We also have our own robust suite of helpers to ensure timezones are displayed consistently regardless of server/client drift.Submitted via Developer Signals
Ugoku commentedon Sep 15, 2026
What I want to do with this feature
I want to use a better API than the Date API, without resorting to 3rd party libraries
Workarounds currently used
We currently use the legacy Moment.js library, which is 150 KB in size and no longer maintained.
mirojones commentedon Sep 17, 2026
What I want to do with this feature
I want to use
Temporal.Durationto display the time passed on a video in MM:SS format.What I'm having to do in the meantime
I use
Math.floor()and/to convert thecurrentTimeto a human-readable format.anthonymhumphreys commentedon Sep 21, 2026
What I want to do with this feature
const tmpdzt = Object.freeze(dzt);
What I'm having to do in the meantime
const tmpEpochMilliSecs = dzt.epochMilliseconds
Cipscis commentedon Sep 30, 2026
What I want to do with this feature
I want to represent dates without time or time zone information attached.
What I'm having to do in the meantime
I'm using a mix of custom
{ year: number; month: number; day: number; }objects andYYYY-mm-ddstrings, and need some custom functions for checking if a date in this representation aligns with the current day based on the user's time zone.