Closed Bug 402233 Opened 18 years ago Closed 17 years ago

Incorrect Event times on Oct 28, 2007

Categories

(Calendar :: Internal Components, defect)

x86
Windows XP
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INCOMPLETE

People

(Reporter: rgnewton, Unassigned)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.8) Gecko/20071008 Firefox/2.0.0.8 eMusic DLM/4.0_1.0.0.1 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.8pre) Likely related to case 399616 which is listed as fixed. Behavior in Version 0.5 was similar to that reported in 399616, the displayed time in the calendar view (month) was an hour off of the time shown in the event dialog. In the current version (0.7) the time selected in the time select dialog is advanced by 2 hours when displayed in the event dialog. However, the time displayed in the month view now agrees with that shown in the event dialog. Current Time Zone: America/Denver Reproducible: Always Steps to Reproduce: 1. Right click Oct. 28/07 and choose New Event 2. Click the start time selection arrow (button). 3. Choose a start time. Actual Results: 4. Time displayed is advanced 2 hrs. from that selected. Expected Results: Time should be displayed as selected timezone set to America/Denver
Hi Robert, do you have the latest windows timezone fixes? We've seen a few of these bugs due to not having the latest timezone fix, thus making windows not realize that the DST shift is occurring later this year.
Is the bug still valid? Can you test it with latest 0.8pre build?
Sorry, When I install 0.8pre build the display comes up scrambled and I can't run it.
How's 0.9pre ? Describe scrambled? (Screenshot maybe). I still believe this is a timezone issue that was possibly fixed.
No response from reporter. Feel free to reopen the bug report if you can still reproduce. -> Resolving as INCOMPLETE.
Status: UNCONFIRMED → RESOLVED
Closed: 17 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.