Closed Bug 375210 Opened 18 years ago Closed 3 years ago

Revisit alarm dialog dismissal/snooze user experience

Categories

(Calendar :: Alarms, defect)

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

Tracking

(Not tracked)

Status:
RESOLVED INVALID

People

(Reporter: mattwillis, Unassigned)

References

Details

(Whiteboard: [not needed beta][no l10n impact])

Spin off from bug 355755 > c) the right fix for this bug is autosnooze in combination with alarm window > state persistence. Both of those bugs could be fixed here, or it'd be > reasonable to start with autosnooze and spin off state persistence into a bug > for later.
Using Sunbird 0.8pre (20071215) closing the dialog now silently snoozes all reminders still shown in the dialog. This behavior was probably introduced with Bug 341576.
Depends on: 341576
Christian will be thinking about how this should best be solved. I'm not sure what is meant with "alarm window state persistance".
IMHO a good and reasonable solution would be to just autosnooze in 1 second, or maybe 1 minute... It would assure the visibility of the same alarms on next startup or after restart - I would agree to not care about the state of the dialog (minimized, item order, ...) - the main goal is to be reminded to the remaining alarms!
Does the "alarm window state persistance" means that the alarm window would reappear on closing and restarting?
Flags: blocking-calendar1.0+
Whiteboard: [not needed beta][no l10n impact]

I don't knwo that this is still an issue

I'm not sure if this is any help.

  • I created an event with a reminder "0 minutes before" the event in my Home calendar.
  • Quit Thunderbird 91.8.0 on Fedora Linux when the reminder triggered without dismissing it.
  • The reminder closed when quitting Thunderbird.
  • It did not reopen and trigger upon restarting Thunderbird.
  • It did trigger about 5 minutes after restarting.
  • Repeated the process of quitting and restarting Thunderbird, and the reminder triggered again after about 5 minutes.

Repeated the process with my Google calendar with the same results.

This bug does not seem actionable. Needs more context. The UX around the alarm dialog does need to be reviewed but will likely happen elsewhere.

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