Skip to content

timeZone

The IANA zone the calendar draws its days and hours in.

TypeZoneId — string
Defaultthe browser's time zone — said once (zone-from-browser)
Live update (update())Yes
Declared inpackages/core/src/kernel.ts

Every event keeps its own zone: 2026-10-22T10:00[America/Chicago] is ten o’clock in Chicago, whatever the calendar shows. timeZone decides where that moment falls on screen — at 17:00 in a calendar set to 'Europe/Paris', at 10:00 in one set to 'America/Chicago'. Days are that zone’s days: a day of 23 or 25 hours when its clocks change.

Give an IANA name ('Europe/Paris', 'Africa/Algiers', 'UTC'), never a bare offset: an offset has no clock changes. Left out, the calendar uses the browser’s zone and says so once (zone-from-browser, through onProblem or the console) — a phone set to Tokyo would draw Algiers’ 14:00 at 22:00. Pass Temporal.Now.timeZoneId() when the browser’s zone is what you mean.

import { createCalendar } from '@dzcalendar/dom';
const calendar = createCalendar(element, {
timeZone: 'Europe/Paris',
events: [{ id: 'call', title: 'Call Chicago', start: '2026-10-22T10:00[America/Chicago]', duration: { hours: 1 } }],
});
// Later: the same events, drawn in Chicago's hours.
calendar.update({ timeZone: 'America/Chicago' });

In the frameworks it is an input: Angular’s timeZone, React’s timeZone, Vue’s time-zone.

The call is set at 10:00 in Chicago; the calendar, in Paris, draws it at 17:00.