Closed Bug 445796 Opened 16 years ago Closed 16 years ago

Deleting an event without attendees prompts "Notify Attendees" dialog

Categories

(Calendar :: E-mail based Scheduling (iTIP/iMIP), defect)

x86
Windows XP
defect
Not set
normal

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: bv1578, Assigned: dbo)

References

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; it-IT; rv:1.9) Gecko/2008052906 Firefox/3.0
Build Identifier: Lightning 0.9 pre build 2008071619

If you delete an event without attendees created with Lg 2008071619, a "Notify Attendees" dialog appears.
No problem with events created with a previous version.
If you close dialog with "Ok" button Error Console shows four errors:

Error: [Exception... "Component returned failure code: 0x805530df [nsIMsgSend.sendMessageFile]"  nsresult: "0x805530df (<unknown>)"  location: "JS frame :: file:///C:/thunderbirdPortable_09/Data/profile/extensions/%7Be2fda1a4-762b-4020-b5ad-a41df1933103%7D/components/calItipEmailTransport.js :: cietSXM :: line 290"  data: no]
Source File: file:///C:/thunderbirdPortable_09(copia)/Data/profile/extensions/%7Be2fda1a4-762b-4020-b5ad-a41df1933103%7D/components/calItipEmailTransport.js
Line: 290 

Reproducible: Always

Steps to Reproduce:
1. Create a new event without attendees and save it;
2. Delete the event
3. 
Actual Results:  
"Notify Attendees" dialog appears.

Expected Results:  
No dialog window should appear.

Works with Lightning 0.9pre 2008071518
Fails with Lightning 0.9pre 2008071619
Confirmed using Lightning 0.9pre (2008071619) on WinXP with local storage calendar.
Status: UNCONFIRMED → NEW
Component: General → E-mail based Scheduling (iTIP/iMIP)
Ever confirmed: true
Flags: blocking-calendar0.9?
QA Contact: general → email-scheduling
Assignee: nobody → daniel.boelzle
Flags: blocking-calendar0.9? → blocking-calendar0.9+
Depends on: 445728
Fixed with bug 445728.
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
Target Milestone: --- → 0.9
Checked in lightning 2008072203 -> VERIFIED
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.