Using the most recent bricks version. The countdown timer was set to UTC +1 and it showed correctly in the UTC +1 timezone but not in Dubai, where it was 3 hours wrong! Had to take it down and I hope we didn’t loose some of our broadcast audience. Can’t reproduce it right now because I’m in a hurry and under a lot of stress.
Hi @Jonathan,
I’m not sure what you mean by “3 hours wrong”. Dubai is on UTC+4 so it would make sense that the time left someone sees in Dubai would be different from what you would see. Can you help me understand what the issue was?
Hi @charaf
Well it was shown 3h in UTC+1 where it was set and in Dubai there were 6 hours left instead of 3. And no, it doesn’t make sense. If you think about it: You want to set the timer in a specific timezone – but you’d want it to be the same HOUR everywhere. In my example that event which happened at 2pm CET in 3 hours. It did not start 3 hours later as it was shown int he timer in Dubai just because of the different timezone, I mean they don’t live in another dimension where time itself is different. I would think the setting is just for convenience to set it in your own timezone and calculated correctly in any other timezone. Does it makes sense? Sorry if I might sound a bit unclear, am a little overworked.
Hi @Jonathan,
I understand the confusion, and it’s a common one when dealing with time zones. Let’s clarify:
The goal or target time should be universal. So when the countdown time is reached, it should be reached throughout the entire world.
Let’s imagine this scenario: Suppose I have an event at 8pm UTC+0 today. Suppose the current time in UTC+0 is currently 4pm. Which means the event is in 4 hours, right?
In another timezone (e.g. UTC+3), the time is going to be 7pm. The event is going to be happening at 11pm UTC+3 timezone. So there’s still 4 hours left until the event.
So, while the event occurs simultaneously worldwide, the local time at which it happens will differ based on each timezone. For instance, it’s at 8pm UTC+0 and 11pm UTC+3, but in both cases, it’s happening at the exact same moment globally.
In your example, when it’s 2pm CET, it’s a different time in Dubai due to the time zone difference. If it’s 2pm CET (Central European Time, which is UTC+1), then it’s actually 5pm in Dubai (which is UTC+4). The countdown timer calculates the time left until the event based on the user’s local time. So, if there are 3 hours left until 2pm CET, the countdown in Dubai will also show 3 hours left, even though the local time in Dubai will be 5pm when the countdown starts.
Does this help clarify things a bit?
1 Like