496889 - past alarms should be ignored, at least by default

Status: NEW

(Calendar :: Alarms, defect)

Description

[Wolfgang Sourdeau]

User-Agent:       Mozilla/5.0 (X11; U; Linux x86_64; fr; rv:1.9.0.10) Gecko/2009042805 Iceweasel/3.0.9 (Debian-3.0.9-1)
Build Identifier: 20090608035852

if we consider alarms in the past, the option should at least be configurable to the user with this choice:
1. show alarms from the past X days
2. show alarms only for events that haven't expired yet (should be the default, in my opinion)
3. don't show past alarms at all.

Reproducible: Always

Comment 1

[Stefan Sitter [:ssitter]]

The request is probably related to Bug 349673, Bug 276585, Bug 466871.

There exists a preference "calendar.alarms.showmissed" that is available via the preference dialog but not used anymore in the alarm code.

Comment 2

[Wolfgang Sourdeau]

Indeed, those bugs are all related.

I think that a proper solution would be, in the Alarm preference pane add an option that use could select to decide how he would like Lightning to behave.

For events OR tasks, let alarms expires never OR after X days/hours/minutes the beginning OR the end of the related event/task. This option could even be configurable on a per-calendar basis but my guess is that it would not even be useful.

Comment 3

[Martin Schröder [:mschroeder]]

Philipp, what should be done here? We have a UI-visible preference that is not used. Does it make sense to change the alarm code, so we respect the value of the preference again?

Comment 4

[Wolfgang Sourdeau]

Hi Martin,


FYI, I hvae uploaded a patch for the missing preference here: https://bugzilla.mozilla.org/show_bug.cgi?id=496883.

However, pertaining to this bug, the preference is set to true by default while I think if should be the contrary.

Comment 5

[Martin Schröder [:mschroeder]]

Push to comm-central <http://hg.mozilla.org/comm-central/rev/60a433653c6c> (bug 496889) has improved the situation by respecting the preference "calendar.alarms.showmissed" again.

What needs to be done to resolve this bug completely?