Skip to content

Temporal in every engine

  • The core functions, which every industry uses.

GMT runs on every current browser and runtime on this page, and on any older one that meets Install’s requirements. It ships its own Temporal, the community @js-temporal/polyfill, so it does not wait for an engine to build Temporal in.

If you use GMT, there is nothing on this page for you to do. The page tracks the engines themselves. Every week, GMT’s whole test suite runs on each engine’s built-in Temporal and on its time zone and locale data. That shows us where an engine differs from the standard, and the bugs we found go back to the engine’s makers.

A host’s time zone offsets and locale text are the host’s own data. The Temporal specification leaves time zone offsets to the implementation (GetNamedTimeZoneOffsetNanoseconds and GetNamedTimeZoneEpochNanoseconds), and ECMA-402 does the same for locale data. GMT gives the right answer for the data it is handed. So two browsers can show different text for one call, and a browser whose data is older than a time zone release gives that release’s old offsets. Helping fix Temporal lists the cases we found.

ICU is the Unicode library that holds locale text and time zone data. Each engine uses its own copy or the system’s.

Browser or runtimeEngineWhere its ICU and time zone data comes fromWeekly leg
Chrome, Edge, Brave, Opera and Vivaldi on desktopChromiumbundled with the browserchromium
Chrome, Samsung Internet and other Chromium browsers on Android, and Android System WebViewChromiumbundled with the browser, in a smaller data file built for Androidnone
FirefoxGecko and SpiderMonkeybundled with the browserfirefox
Safari on macOSWebKit and JavaScriptCorethe operating systemwebkit-macos
Safari and other browsers on iPhone and iPadWebKit, except where Apple allows another enginethe operating systemwebkit-macos (same engine and Apple’s ICU; iOS’s own data is not tested)
DuckDuckGothe system engine: WebKit on macOS and iOS, Chromium on Windows, Android System WebView on Androidas that enginewebkit-macos or chromium; none on Android
WebKit on Linux (WebKitGTK, WPE)WebKit and JavaScriptCorethe Linux distribution’s ICUwebkit
Node.jsV8bundled with Node (full ICU)node
DenoV8not documentednone
Cloudflare WorkersV8not documentednone
BunJavaScriptCorenot documentednone

Brave, Edge, Opera, Vivaldi and DuckDuckGo are covered on desktop through their engine. No run tests them by name, and no run tests a browser on Android.

Bun runs JavaScriptCore, the engine Safari uses. No weekly run tests Bun, and its time zone and locale data is not documented.

Where each cell comes from:

GMT runs on these too, as long as they meet Install’s requirements, but no weekly run tests their engine or data yet. If GMT gives a wrong answer on one, we want the report.

  • Browser versions older than the one each weekly run installs.
  • Other macOS versions, and iOS itself. The webkit-macos leg runs the macOS version its runner has.
  • Deno, Bun and Cloudflare Workers, which have their own data.
  • Chromium on Android: Chrome, Samsung Internet, DuckDuckGo and Android System WebView. They read the smaller Android data file, which the chromium leg does not load.

The weekly workflow lists every run. Each run’s summary names the engine version it tested and, for webkit-macos, the macOS version. Pulse shows the recent results next to the other checks GMT runs.

© 2026 NorthGuild · Licences

Code examples: MIT-0. Packages: MIT. Third-party data and components: their own licences, credited where they appear. Everything else: © 2026 NorthGuild, all rights reserved.