Open Bug 298350 Opened 19 years ago Updated 2 years ago

calICalendar needs to support getting events by alarm-fires-in-range

Categories

(Calendar :: Internal Components, defect)

defect

Tracking

(Not tracked)

People

(Reporter: shaver, Unassigned)

Details

I'm not sure this should block 0.8: I think we can catch the common case (alarm
is  within, say, a day of the event) by just expanding the range of our search,
and that's enough to fix for the pre-release, IMO.
No longer blocks: lightning-0.1
Joey, might this be something take on when you implement calIAlarm or is this something completely different?
Assignee: pavlov → base
(In reply to comment #2)
> Joey, might this be something take on when you implement calIAlarm or is this
> something completely different?
> 
This would definitely not go in during the initial landing of calIAlarm.  The fix for this bug is different for each provider.  Storage cals need to issue particular database queries, caldav needs to issue particular REQUESTS, and ics is just screwed.  This bug probably depends on calIAlarm, since it that will change the way alarms are stored in the db.
The bugspam monkeys have struck again. They are currently chewing on default assignees for Calendar. Be afraid for your sanity!
Assignee: base → nobody
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.