Open
Bug 1128737
Opened 11 years ago
Updated 3 years ago
Non standard alarm handling - solution proposition
Categories
(Calendar :: Alarms, defect)
Tracking
(Not tracked)
UNCONFIRMED
People
(Reporter: ingo, Unassigned)
Details
User Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/42.0.2288.6 Safari/537.36
Steps to reproduce:
Mozilla has a proprietary alarm handling. It sends X-MOZ-LASTACK and X-MOZ-SNOOZE-TIME for alarm acknowledgements to the CalDAV server and not all of them support this. Plus, even if the server supports this, other clients will not be able to handle this information.
Actual results:
If it is not supported on the server, the alarm popup cannot be snoozed and cannot be dismissed, the popup will pop up for ever.
Notwithstanding the above, other clients will continue to pop up even if snooze or dismiss was selected.
Expected results:
EmClient handles it in a rather elegant way:
snooze for x minutes modifies the original alarm time by x minutes and saves it.
dismiss deletes the alarm.
Every server should be able to handle this and this solution would synchronise alarm across server and all clients without being a mozilla-centric solution.
Can this be implemented that way?
Updated•3 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•