Closed Bug 267198 Opened 20 years ago Closed 19 years ago

changing start time of an event doesn't reset the alarm

Categories

(Calendar :: General, defect)

x86
Linux
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: jwz, Assigned: mostafah)

References

Details

At around 11:55 I added an event; I meant to say "12:45, notify me 15 minutes
before" but instead I entered "12:00".

A minute later, the alarm window popped up.  I realized my mistake, went over to
the calendar window, and fixed the start/end times of the event.

I expected the alarm to pop down as soon as I made this edit; it didn't.

I told it to "snooze 1 minute" hoping that would un-confuse it; it came back in
a minute (at around 11:59) telling me about my 12:45 event.

I'm afraid that if I click the Acknowledge button, it's not going to notify me
at 12:30 like it was supposed to, so I guess I'll just delete the event and
re-add it.

Expected results:

   If an alarm window is up, and the start time or alarm time of the event
   are edited such that, had it been that way all along, the alarm would not
   have gone off yet; then the alarm should be withdrawn and re-scheduled
   for the now-appropriate time.
Likewise, if I delete the event from the calendar, the alarm notification should
de-post (since now it's a notification for an event that doesn't even exist any
more.)
*** Bug 249533 has been marked as a duplicate of this bug. ***
QA Contact: gurganbl → general
Nightly builds now work as requested, although admittedly, this can cause some confusion, since moving events short distances doesn't re-trigger the alarm, but moving it long distances does.

WFM.
Status: NEW → RESOLVED
Closed: 19 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.