Closed
Bug 504903
Opened 15 years ago
Closed 15 years ago
Accepting event invitations no longer asks which calendar to add to
Categories
(Calendar :: E-mail based Scheduling (iTIP/iMIP), defect)
Calendar
E-mail based Scheduling (iTIP/iMIP)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: Parasyte, Unassigned)
Details
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.1pre) Gecko/20090630 Shiretoko/3.5.1pre Build Identifier: This feature was added in Bug 351745 - iMIP bar should ask user what calendar to add invitation to Reproducible: Always Steps to Reproduce: Same STR and results as Bug 351745 comment #0
Reporter | ||
Updated•15 years ago
|
Version: unspecified → Trunk
Reporter | ||
Comment 1•15 years ago
|
||
Build Identifier: Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-US; rv:1.9.1.1) Gecko/20090715 Lightning/1.0pre Thunderbird/3.0b3 and Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.1) Gecko/20090715 Lightning/1.0pre Thunderbird/3.0b3 Lightning version is latest-comm-1.9.1; 20090717 on each platform.
Comment 2•15 years ago
|
||
I cannot confirm, it works fine for me. Upon clicking the Accept button the Select Calendar dialog shows up for picking one of the three available local calendars. Please provide *detailed* steps to reproduce the issue starting with a fresh profile. Using Lightning 1.0pre (BuildID: 20090717032138) with Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.1pre) Gecko/20090717 Shredder/3.0b4pre (BuildID: 20090717034003).
Reporter | ||
Comment 3•15 years ago
|
||
I have created a second calendar in a new profile which I associate with email address "none". This calendar is filtered from the list of possible calendars to add to; Since only the default "Home" calendar has an associated email address, it's automatically chosen as the target calendar. Resolving WFM. Calendars with no associated email address should probably be filtered from iMIP invitations.
Status: UNCONFIRMED → RESOLVED
Closed: 15 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•