imbahub
Menu +
US
Talk to us
IMBAHUB / Knowledge & guides

Event times shift incorrectly at daylight-saving changes

The same local start time has the wrong relationship to that date’s zone.

Event times shift incorrectly at daylight-saving changes
  1. Starting condition

    A time without a zone can mean different things to organisers and visitors. A website needs to distinguish a fixed instant from a recurring local time.

  2. Implementation

    Choose an ordinary day and dates around spring and autumn transitions. Compare source data, stored instant and display in two zones. A local hour can be missing or repeated; the system needs an explicit decision.

  3. Verification

    Ordinary dates and transition cases agree across the page and calendar export.

  4. Decision

    Use the date’s actual zone rules and define how ambiguous local times are selected. Formatting changes or translated month names do not repair the time model.

Ordinary dates and transition cases agree across the page and calendar export.

Which check determines the next step?

Use the date’s actual zone rules and define how ambiguous local times are selected. Formatting changes or translated month names do not repair the time model.

Start with a reproducible failure

A time without a zone can mean different things to organisers and visitors. A website needs to distinguish a fixed instant from a recurring local time.

Use a small controlled test to separate a symptom from its cause. Record the starting state, affected URL and observed outcome so that another person can repeat the check.

Collect evidence before changing anything

Choose an ordinary day and dates around spring and autumn transitions. Compare source data, stored instant and display in two zones. A local hour can be missing or repeated; the system needs an explicit decision.

Fictional example: A recurring webinar should start at nine in the organiser’s zone. A fixed UTC offset makes the next session display an hour incorrectly after the transition.

CheckExpected outcome
Starting conditionThe same local start time has the wrong relationship to that date’s zone.
ImplementationChoose an ordinary day and dates around spring and autumn transitions. Compare source data, stored instant and display in two zones. A local hour can be missing or repeated; the system needs an explicit decision.
VerificationOrdinary dates and transition cases agree across the page and calendar export.

Fix the cause and repeat the test

Use the date’s actual zone rules and define how ambiguous local times are selected. Formatting changes or translated month names do not repair the time model.

Repeat the same test after the change and add a nearby case that already worked. One successful case establishes that task in those conditions; it does not certify the whole website.

What the test establishes

Ordinary dates and transition cases agree across the page and calendar export.

Sources and further reading

Questions, answered

Is passing an automated test enough?

Combine technical checks with the actual visitor task. Document the environment, conditions and remaining limitations.

Which check determines the next step?

Use the date’s actual zone rules and define how ambiguous local times are selected. Formatting changes or translated month names do not repair the time model.

IMBAHUB

Let’s plan your website

Describe the website task and the failure or development requirement you want to scope.

Talk to us
Existing English product interface with fictional demonstration content; reused for the US website.

Existing English product interface with fictional demonstration content; reused for the US website.