Closed
Bug 306982
Opened 19 years ago
Closed 19 years ago
Alarms not working with floating dates
Categories
(Calendar :: Internal Components, defect)
Calendar
Internal Components
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: mvl, Assigned: mvl)
References
Details
Attachments
(1 file)
|
3.08 KB,
patch
|
dmosedale
:
first-review+
|
Details | Diff | Splinter Review |
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•19 years ago
|
||
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•19 years ago
|
||
Comment on attachment 194785 [details] [diff] [review]
patch v1
r=dmose
Attachment #194785 -
Flags: first-review?(dmose) → first-review+
|
|
Assignee | |
Comment 3•19 years ago
|
||
patch checked in
Status: NEW → RESOLVED
Closed: 19 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•