Bugzilla

(In reply to Magnus Melin [:mkmelin] from comment #2)
> But, it only applies when you're not an invitee, right? And once you rsvp'd you will be on the list (at least locally, servers may choose not to accept it). So for processing at that time, you will always find yourself in the attendees list and things will work. Or?

Currently we always assume the invited attendee is the identity on the calendar. The attendees list is more or less consulted to ensure that identity is also listed there, if not, we either assume no invited attendee or in some areas use the default. Things sort of like this but I'm sure there are subtle bugs. For example; I noticed that when I accept an event to a calendar, change the calendar's identity, then delete the event, I don't get the "Send email" prompt and the cancellation does not go out.

I think it's a good idea in general to keep track of how an invitation was received on the item instead of computing it every time.

(In reply to Magnus Melin [:mkmelin] from comment #2)
> But, it only applies when you're not an invitee, right? And once you rsvp'd you will be on the list (at least locally, servers may choose not to accept it). So for processing at that time, you will always find yourself in the attendees list and things will work. Or?

Currently we always assume the invited attendee is the identity on the calendar. The attendees list is more or less consulted to ensure that identity is also listed there, if not, we either assume no invited attendee or in some areas use the default. Things sort of work like this but I'm sure there are subtle bugs. For example; I noticed that when I accept an event to a calendar, change the calendar's identity, then delete the event, I don't get the "Send email" prompt and the cancellation does not go out. 

I think it's a good idea in general to keep track of how an invitation was received on the item instead of computing it every time.