Custom repeated event times shifted at daylight savings time/standard time changes

RESOLVED INVALID

Status

Calendar
Internal Components
--
major
RESOLVED INVALID
8 years ago
8 years ago

People

(Reporter: Shepsl Topaz, Unassigned)

Tracking

Details

(Reporter)

Description

8 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.7) Gecko/20091221 Firefox/3.5.7 (.NET CLR 3.5.30729)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.18pre) Gecko/20080917 Sunbird/0.9

Entered a (weekly) repeated event with custom repeat required to specify end date. At daylight savings time event time is changed to one hour later. At return to standard time even time is changed to one hour earlier. Note: Did a test event using simple (weekly) repeat and problem does not occur. Bug must be in daylight savings/standard time processing. Event time should not change.

Reproducible: Always

Steps to Reproduce:
1. enter new event
2. for repeat select custom
3. specify end date
4. save
Actual Results:  
When I browsed through the calendar I see the event time changed after/at daylight savings/standard time changes

Expected Results:  
Event time should have been the same throughout
What calendar type are you using (local, caldav, google calendar, ...)

What timezone is Lightning set to? Did you specify a different timezone on event creation?

Does this still happen with the latest 1.0b2pre nightlies?
(Reporter)

Comment 2

8 years ago
(In reply to comment #1)
> What calendar type are you using (local, caldav, google calendar, ...)
> 
> What timezone is Lightning set to? Did you specify a different timezone on
> event creation?
> 
> Does this still happen with the latest 1.0b2pre nightlies?

Might as well put this one to rest. From another calendar-related bug reported it seems for the online calendar I was using (under Horde) had a flaw in exported data. I switched to Google calendar and now have no problem.

Thanks!
Status: UNCONFIRMED → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.