Temporal in every engine
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.
Why each engine is tested
Section titled “Why each engine is tested”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.
Browsers and runtimes
Section titled “Browsers and runtimes”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 runtime | Engine | Where its ICU and time zone data comes from | Weekly leg |
|---|---|---|---|
| Chrome, Edge, Brave, Opera and Vivaldi on desktop | Chromium | bundled with the browser | chromium |
| Chrome, Samsung Internet and other Chromium browsers on Android, and Android System WebView | Chromium | bundled with the browser, in a smaller data file built for Android | none |
| Firefox | Gecko and SpiderMonkey | bundled with the browser | firefox |
| Safari on macOS | WebKit and JavaScriptCore | the operating system | webkit-macos |
| Safari and other browsers on iPhone and iPad | WebKit, except where Apple allows another engine | the operating system | webkit-macos (same engine and Apple’s ICU; iOS’s own data is not tested) |
| DuckDuckGo | the system engine: WebKit on macOS and iOS, Chromium on Windows, Android System WebView on Android | as that engine | webkit-macos or chromium; none on Android |
| WebKit on Linux (WebKitGTK, WPE) | WebKit and JavaScriptCore | the Linux distribution’s ICU | webkit |
| Node.js | V8 | bundled with Node (full ICU) | node |
| Deno | V8 | not documented | none |
| Cloudflare Workers | V8 | not documented | none |
| Bun | JavaScriptCore | not documented | none |
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:
- Chromium bundles its own ICU data, and builds a separate, smaller data file for Android with only minimal calendar data (Chromium ICU notes). The
chromiumleg runs the desktop data. - Brave, Edge, Opera, Vivaldi and Samsung Internet are built on Chromium: Brave, Edge, Opera, Vivaldi and Samsung Internet.
- Firefox keeps its own copy of ICU (
intl/icu) and of the time zone data (intl/tzdata). Its engines are Gecko and SpiderMonkey. - Apple’s WebKit links the operating system’s ICU: the WebKit source references
libicucore.dylib, which Apple’s open-source ICU builds. - WebKit on Linux uses the ICU the distribution provides: see the WebKitGTK and WPE build files.
- On iPhone and iPad, browsers must use WebKit unless Apple grants an entitlement: App Review Guidelines and BrowserEngineKit.
- DuckDuckGo uses the system engine: WebKit on Mac, WebKit on iPhone and iPad, WebView2 on Windows, and on Android the Android WebView, which Chromium implements.
- Node ships full ICU data (Node Intl) and runs on V8.
- Deno is built on V8, Cloudflare Workers run V8, and Bun runs JavaScriptCore. None of the three documents where its ICU or time zone data comes from.
No weekly run yet
Section titled “No weekly run yet”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-macosleg 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
chromiumleg does not load.
Where the results are
Section titled “Where the results are”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.