Alarms not working with floating dates

RESOLVED FIXED

Status

Calendar
Internal Components
RESOLVED FIXED
13 years ago
13 years ago

People

(Reporter: Michiel van Leeuwen (email: mvl+moz@), Assigned: Michiel van Leeuwen (email: mvl+moz@))

Tracking

Details

Attachments

(1 attachment)

When the startdate of an event is floating (now the default for sunbird), alarms
don't work. The calculation of the timeout for the alarm to be fired is off by
the gmt offset.
(Assignee)

Comment 1

13 years ago
Created attachment 194785 [details] [diff] [review]
patch v1

getInTimezone on a floating datetime doesn't change actually, because the time
is the same in all timezones. That's what floating means. But the current time
does change when getting in utc. So there is a difference. This patch works
around it.
Attachment #194785 - Flags: first-review?(dmose)

Comment 2

13 years ago
Comment on attachment 194785 [details] [diff] [review]
patch v1

r=dmose
Attachment #194785 - Flags: first-review?(dmose) → first-review+
(Assignee)

Comment 3

13 years ago
patch checked in
Status: NEW → RESOLVED
Last Resolved: 13 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.