Daylight Saving

Created on 25 March 2024, 6 months ago
Updated 14 April 2024, 6 months ago

Problem/Motivation

We have a content type that includes a smart date field, and users create recurring meetings. Once a content is created, and the user's timezone set in their profile is New York, for example, and the timezone in the content (Smart Date component) is set to Paris, for example, we are observing an issue with the timezone. Daylight Saving Time (DST) is being calculated twice.

Steps to reproduce

- Set the user profile timezone to New York.
- Select the startDate enDate, and Set the time zone to Australia for example.
- Verify the times before and after the Daylight Saving, The times after DST are incorrect.

NOTE: For some time zones, even if we set the user profile as the selected timezone in the smart date component, The issue still exists.

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

💬 Support request
Status

Active

Component

Smart Date Recur

Created by

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @lmaali
  • 🇨🇦Canada mandclu

    Based on my testing, I believe that Smart Date is working properly, but the combination of time zones you have chosen introduces some unexpected results, because Australia's DST goes in the opposite direction and at different times. To test this theory, I followed your steps to reproduce, for an event recurring monthly for 11 times, so starting before and ending after DST in North America (notice the timezones listed):

    To confirm, I used worldtimebuddy.com to check some of these conversions, and all three that I checked confirmed that the conversions are correct:

    I would say that Smart Date is working properly, but some combinations of time zones lead to a complex influence for DST.

  • 🇨🇦Canada mandclu

    Based on my testing, I believe that Smart Date is working properly, but the combination of time zones you have chosen introduces some unexpected results, because Australia's DST goes in the opposite direction and at different times. To test this theory, I followed your steps to reproduce, for an event recurring monthly for 11 times, so starting before and ending after DST in North America (notice the timezones listed):

    To confirm, I used worldtimebuddy.com to check some of these conversions, and all three that I checked confirmed that the conversions are correct:

    I would say that Smart Date is working properly, but some combinations of time zones lead to a complex influence for DST.

Production build 0.71.5 2024