Closed Bug 253169 Opened 21 years ago Closed 21 years ago

Alarm acknowledgement does not get published to remote calendars (even when auto-publish in enabled)

Categories

(Calendar :: General, defect)

x86
Linux
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 212076

People

(Reporter: blabj, Assigned: mostafah)

Details

User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7) Gecko/20040705 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7) Gecko/20040705 When an alarm event occurs on a remote calendar (which is subscribed to with "Publish events automatically"), and the alarm is acknowledged, the X-MOZILLA-LASTALARMACK does not get published to the remote calendar, unless it is forced with a "Publish Entire Calendar" operation. Reproducible: Always Steps to Reproduce: 1. Create an event with an alarm on a remote calendar 2. When the alarm pops up, click Acknowledge Actual Results: The local and remote calendar files are then out of sync - if you exit and restart mozilla, alarm will pop again.. and so on until you "Publish Entire Calendar". Expected Results: When "Acknowledge" is clicked, the event should be published immediately to the remote calendar.
*** This bug has been marked as a duplicate of 212076 ***
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago
Resolution: --- → DUPLICATE
The bugspam monkeys have been set free and are feeding on Calendar :: General. Be afraid for your sanity!
QA Contact: gurganbl → general
You need to log in before you can comment on or make changes to this bug.