Dismissing alarm from a shared Google calendar interferes with that from a different account
Categories
(Calendar :: Alarms, defect)
Tracking
(Not tracked)
People
(Reporter: bug-str, Unassigned)
References
(Blocks 1 open bug)
Details
Steps to reproduce:
Two computers use Thunderbird Calendar with two different Google accounts, A and B (one for each computer).
Google Account A has a private Google calendar shared (with read-write access) with the account B.
Pop-up alarms are configured on both computers.
Actual results:
When the alarm is dismissed on one computer/one account, on the other computer/account, attempt to dismiss the alarm pops up a confirmation dialogue "Discard my changes and reload" or "Submit my changes anyway".
Expected results:
The alarms for different users with different Google accounts (even if sharing the same Google calendar) should not interfere with each other.
In my opinion, this annoying dialogue should not appear even for two computers using the same Google account: there is no effective change to the event (i.e. that has an effect on the event information or future behavior of the alarms) that occurs upon dismissing the event on one computer.
But even if I am missing some important aspect here, - it definitely should NOT play a role when two different people with different accounts involved. (Actually, there is also a privacy issue here.)
I would suggest that when you dismiss an alarm, Calendar should not do any modification to the event. This would avoid numerous other bugs related to the alarm dismissal (See e.g. another recently filed Bug 1761284 ) and the necessity for the kludges to work around those problems, e.g. when working with read-only calendars, or events created by another user with some special scenario. see e.g. Bug 1727123, Bug 1733447, ... )
Note, that a few mobile Calendar clients (for Android) that we are using with the same shared Google calendar, via different accounts that have access to it, do not have this problem and the constant need of voodoo magic to dismiss an alarm.
|
||
Comment 1•3 years ago
|
||
Do you still see this when using version 102 or newer?
Does bug 1761284 accurately describe your issue?
Bug 1761284 probably have a certain overlap with this one in the mechanism that is responsible for the behavior (the fact that dismissal of the alert updates something in the event itself), but they are about separate issues:
This one is about different accounts sharing the same calendar, - whose alerts behavior is interdependent (while it shouldn't be).
That other bug is about the behavior within the same account - while accessed from different computers or on one computer via different methods (GData & Provider for Google Calendar).
I am not sure which version is running on different computers. On, mine I just updated it to 102.6.1, but I am not sure what it was before. The computer with a different account was on 91.x, I just updated it to 102, so, I am yet to see.
Description
•