Open
Bug 349673
Opened 18 years ago
Updated 2 years ago
Alarm dialog shown for new events that are scheduled in the past
Categories
(Calendar :: Alarms, defect)
Tracking
(Not tracked)
NEW
People
(Reporter: buchner.johannes, Unassigned)
References
Details
(Whiteboard: [no l10n impact])
A "Calendar Alarm" window pops up on creating a view.
Also the view isn't refreshed (maybe another bug).
Reproduce:
1) start Sunbird.
2) on today, Day View, create a new event: Enter a title, leave all the other settings.
3) a popup is opened, maybe behind the front window, named "Calendar Alarm"
There you can "Dismiss the alarm".
4) The Task is not shown in the day, you have to refresh the view, e.g. by rotate.
5) Moving, Resizing doesn't work on the event instantly (the view is not refreshed)
Reporter | ||
Comment 1•18 years ago
|
||
This is on Windows XP,
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a1) Gecko/20060821 Calendar/0.3a2+
2006082104
Comment 2•18 years ago
|
||
Have you set Preferences -> Alarms -> Default Alarm to On? In that case every new event/task has an alarm set. If you now create the event/task on current day and before current time the alarm will fire immediately because the alarm time is already over. From this point of view the behavior is expected.
Reporter | ||
Comment 3•18 years ago
|
||
(In reply to comment #2)
> Have you set Preferences -> Alarms -> Default Alarm to On?
Yes.
> In that case every
> new event/task has an alarm set. If you now create the event/task on current
> day and before current time the alarm will fire immediately because the alarm
> time is already over.
This is stupid. I create an event and am notified about it? I assume I know about the event if I enter it.
Also, the dialog should pop up in the front.
Comment 4•18 years ago
|
||
(In reply to comment #3)
> > In that case every
> > new event/task has an alarm set. If you now create the event/task on current
> > day and before current time the alarm will fire immediately because the alarm
> > time is already over.
> This is stupid. I create an event and am notified about it? I assume I know
> about the event if I enter it.
Then change the setting.
>
> Also, the dialog should pop up in the front.
>
That's bug 202620.
Any reason this shouldn't be marked invalid?
Reporter | ||
Comment 5•18 years ago
|
||
(In reply to comment #4)
> Any reason this shouldn't be marked invalid?
This also pops up when making events in the past?
I tried an repeated event (daily, 5 times, one week ago) and got 5 alarms. I want it for future events, but don't want it for events in the past.
Comment 6•18 years ago
|
||
(In reply to comment #5)
> I want it for future events, but don't want it for events in the past.
Updating summary to reflect the real issue here for future discussion.
Summary: calendar Alarm popups constantly → Alarm dialog shown for new events that are scheduled in the past
Updated•18 years ago
|
Component: General → Alarms
QA Contact: general → alarms
Comment 7•18 years ago
|
||
I agree this is annoying behaviour of the UI.
Real users do not only enter events in the future, but also may enter events in the past, like in a paper based diary, as a means of recording what actually happened as distinct from what was tentatively planned. If I create a new event in the past, it is pointless giving me an alarm, but I do still want alarms for future events. This applies whether the new event (or dragged & dropped event) is now an hour, or even a day/week/month in the past - there should be no alarm, I already know it's in the past.
Additionally, alarms seem generally erratic on Win XP with Sunbird 0.3 at the best of times, but that is a separate issue.
Comment 10•15 years ago
|
||
We could possibly fix this bug by setting X-MOZ-LASTACK to the event creation date for new events created by the event dialog that have an alarm. Stefan, do you think that makes sense?
Updated•15 years ago
|
Flags: blocking-calendar1.0+
Whiteboard: [not needed beta][no l10n impact]
Comment 11•14 years ago
|
||
I don't think we should block 1.0 on this, nor am I sure that its wise to put the alarm stamps on each event with alarms we create.
Flags: blocking-calendar1.0+
Whiteboard: [not needed beta][no l10n impact] → [no l10n impact]
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•