Closed Bug 974847 Opened 11 years ago Closed 11 years ago

Alarms for old events (expired since 1 month ago) are notified

Categories

(Calendar :: Alarms, defect)

Product:
Calendar
Component:
Alarms
Version:
Lightning 2.6.4
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED DUPLICATE of bug 496889

People

(Reporter: sberthelot, Unassigned)

Details

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:27.0) Gecko/20100101 Firefox/27.0 (Beta/Release) Build ID: 20140204080215 Steps to reproduce: Multiple ways to get this problem : - create an event in the past with an alarm - import a remote calendar with pasts events having an alarm and not X-MOZ-LASTACK set Actual results: A notification in shown to dismiss/snooze the alarm Expected results: Nothing, expired alarms should be ignored
To be more complete, here are two items that I want to add : - on calendar-js/calAlarmService.js:273 we have "start.month -= 1;" , why do we notify the user about past reminders at all ? The purpose of a reminder to me is to not let you miss something that happens now or is going to happen soon ... - on remote calendars that do not necessarily export or keep the "non-standard" X-MOZ-LASTACK flag (or purge it, like Horde : see http://bugs.horde.org/ticket/12984 ) alarms for past events get notified again each time the calendar is refreshed. It gets even worse on read-only remote calendars since we cannot set this flag at all
There's a preference setting on the Reminders tab for "Show missed reminders".
OK, found it (calendar.alarms.showmissed) but it seems to be true by default. Setting it to false seems to not fire old alarms. It would be certainly be better to set it off by default. Can you confirm the default state of this pref ?
Yes, the value is true by default because otherwise users will not be informed about missed events. If you or another user decide to not be informed just flip the checkbox in the preference dialog.
I still cannot understand the point of informing the user about past (=expired) events. The "missed" part depends upon the backend used and many remote ones don't provide this status extension, and even some like Horde purge it for old (< now) events. I have hundreds of computers that needs this preference changed at least, any mean to do it "cleanly" in the meantime ?
Status: UNCONFIRMED → RESOLVED
Closed: 11 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.