Creating an event in the past triggers notifications
Categories
(Calendar :: General, defect)
Tracking
(Not tracked)
People
(Reporter: benjamin, Unassigned)
Details
User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:100.0) Gecko/20100101 Firefox/100.0
Steps to reproduce:
As is best-described by #1741800, Thunderbird needs to be a bit more sensitive about triggering notifications for events that have already happened.
Here is a similar case.
- Create some notification setting for an active calendar (either for the calendar or globally)
- Navigate to the calendar view
- By clicking and dragging the mouse cursor, create an event in the past (more backwards in the past than the threshold of the notification, so if we have notifications 1 day before, create the event more than 1 day before)
- Notice that creating the event immediately spawns the notification leading to the field for naming the event being de-focused and the event is called "Untitled". Now we have to open the event and click edit.
Actual results:
We received a useless notification
The event was mis-named "Untitled"
We have to open the event in order to edit it
Expected results:
No notifications should be triggered by creating a new event in the past
|
||
Comment 1•3 years ago
|
||
I think it's the same as bug 1741800. How would thunderbird know you were going to come back and edit the event?
|
Reporter | |
Comment 2•3 years ago
|
||
Just coming back to this, I think that the user also has good work-arounds:
If creating an event in the past is noisy, then temporarily removing default notification settings from the calendar should work.
Sounds good to close it, not much benefit of fixing this!
Description
•