thunderbird calendar miss interpret time hour change due to winter time shift at 2022-10-30, Europe - Spain
Categories
(Thunderbird :: General, defect)
Tracking
(Not tracked)
People
(Reporter: jordi.ferran, Unassigned)
Details
Brief: noticed time shift due to winter time change; date: 2022-10-30. Means: fix time -1 hour.
Version: bug found using mozilla, program thunderbird, version 102.4.1 (64 bits, on gnu-linux ubuntu-18.04-lts).
Bug: use calendar, create event, edit begin time set 09:00h A.M.;
fails to notice the -1 hour fix (daylight saving); means creates event with start time at 08:00h A.M.; instead of 09:00h A.M.; tip: the operating system is working fine, the time shift is already applied.
Tip: reboot machine computer, and operating system, to verify it has no relation. Bug persists after reboot.
Tip: use calendar, use mouse left-click to move event around the time vertical axis; it is relocated OK. Function is working fine.
Bug: use calendar, use mose left-click to resize existing event changing the end-time field-value; example use case: create event 2 hours, see start-time is wrong, use mouse to drag and drop to move event one hour backwards, then use mouse left-click drag-n-drop to resize end-time to shift ending by -1 hour; it fails to do so and keep the event timeframe with same end-time value. Seems to be linked to the same error, fails to notice one hour shift due to winter daylight time saving. With event 3 hours window, a resize -2 hours is resized as -1 hour.
Bug: also notice create task 13:00h to 20:00h, event details shows 13-20h; but event is displayed in calendar window as 14:00h to 20:00h. Function event details on time start and ending values, do not match what is shown; means event starts at 13:00h but in visual windows starts at 14:00h.
Conclusion: program changes introduced a bug; function to manage winter time savings now fails; never did it before; after using the program for decades.
Context info:
All noticed in country Spain, following DayTime savings in Zone/Area Europe in date: 2022-10-30; first time noticed; using program everyday. Yesterday in 2022-10-29 it was working fine.
Updated•3 years ago
|
Description
•