Closed Bug 428249 Opened 17 years ago Closed 17 years ago

New event created one day ahead of date clicked

Categories

(Calendar :: Sunbird Only, defect)

x86
All
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 428715

People

(Reporter: gentoo.kalos, Unassigned)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.13) Gecko/20080311 Firefox/2.0.0.13 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.13pre) Gecko/20080331 Sunbird/0.8 In Sunbird 0.8, when I double-click a certain date to create a new event, the start date and end date are usually the day that I double-clicked. For instance, if I click on 10 April 2008, the start and end dates will be 10 April 2008. However, if I try to create a new event within 1 hour of midnight (local time), the start and end dates are one day ahead. For instance, if it is 10 April 2008 any time (locally) between 23:00 and 23:59, the start and end dates will be for the next day (11 April 2008) by default. I believe this issue may be related to timezones, considering it seems to be limited to that particular hour. I created my first calendar long ago and incorrectly set the timezone to America/Belize instead of my local time. I haven't switched to the correct timezone because it changes everything currently on my calendar to the wrong time. Reproducible: Always Steps to Reproduce: 1. Set timezone to any zone -1 hour from ACTUAL local time 2. Set system clock to any time between 23:00 and 23:59 3. Double-click a date to create a new event Actual Results: The default start and end dates are one day ahead of the date clicked. Expected Results: The default start and end dates are the same as the date double-clicked to add a new event. I see this same issue on all of my machines (with Sunbird 0.8): 4 flavours of Linux (Gentoo, Arch, PCLinuxOS, LFS) Windows (XP and Vista) Mac (OS X) Also, I understand that there is a good chance to my timezone being incorrect. If the solution is to change the timezone to the correct one, how can one avoid the timezone switch from changing all the event times previously entered?
EDIT: Also might be related to Daylight Savings Time.
The current intended behavior is to set the time to the next full hour. That means if you create the event at 14:xx the default time will be set to 15:00. If you create the event at 23:xx the default time will be set to 00:00. This moves the event to the next day.
Status: UNCONFIRMED → RESOLVED
Closed: 17 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.