Closed Bug 461511 Opened 15 years ago Closed 13 years ago

If 'Directory Server' is enabled it is not possible to add more then one attendees at once


(Calendar :: General, defect)

Not set


(Not tracked)



(Reporter: andreas.treumann, Assigned: standard8)



(Keywords: regression, Whiteboard: [not needed beta][no l10n impact])


(2 files)


- go to Prefrences/Composition/Addressing
- check 'Directory Server'
- create a new event
- open the attendees dialog
- try to invite more than one attendees


- it's not possible to add more then one attendee without closing the dialog


- it should be possible to add more than one attendee


- always
Assuming this is the code I think it is (LDAP directory servers) that has been copy & pasted from MsgComposeCommands.js then before doing much work on it, it would be better to wait for my work on bug 452232 which is intending to greatly simplify the code required for LDAP autocomplete.
Depends on: 452232
Flags: blocking-calendar1.0+
I could not reproduce this issue with the latest nightlies. bug 452232 will unfortunately not block tb3.
Keywords: qawanted
Whiteboard: [need confirm]
This partially fixes the problem - input.syncSessions is undefined because we're not replacing the dummy element early enough, and hence the elements aren't connected right.

There are still significant issues with LDAP with this patch, and which seem to stop shutdown working correctly as well. My only thought is that the LDAP sessions aren't quite being handled correctly, and comparison of the xml file with the existing LDAP setup code may help.
Comment on attachment 359248 [details] [diff] [review]
[checked in] Partial Patch

If this patch improves the situation, I'm fine with that. Do you think fixing the attendees dialog to work correctly with ldap is something feasible for 1.0 (i.e amount of work vs amount of improvement) ?
Attachment #359248 - Flags: review+
Mark, can you please check this in?
Assignee: nobody → bugzilla
Keywords: checkin-needed
Whiteboard: [need confirm] → [not needed beta][no l10n impact]
I'll check this in once the tree reopens - I don't want to push now as we are in the critical stage.
Keywords: checkin-needed
Whiteboard: [not needed beta][no l10n impact] → [not needed beta][no l10n impact][has patch to check in]
Comment on attachment 359248 [details] [diff] [review]
[checked in] Partial Patch

Checked in:

Leaving open for now as it doesn't fix the problem fully.
Attachment #359248 - Attachment description: Partial Patch → [checked in] Partial Patch
Whiteboard: [not needed beta][no l10n impact][has patch to check in] → [not needed beta][no l10n impact]
Seems the checkin for this bug fixed Bug 459905 too. Thanks!
So, what exactly is left from this bug? Is the bug summary still valid? Do we really need to fix this for 1.0 ?
I can still confirm this issue, and can only auto-complete an attendee once. IMHO this is an important feature and used quite often, thus we shouldn't release without fixing it.
I've attached a proposed patch to fix the other half of this bug (more than one invitee auto-completion). I agree with Daniel that this is an important issue. I understand that there may be work on implementing this through some new way, but for the time being it would be great to see the current implementation work as needed.
Comment on attachment 421171 [details] [diff] [review]
many user LDAP auto-complete patch

Pushing in Philipp's review queue to get some feedback for Aaron.
Attachment #421171 - Flags: review?(philipp)
Comment on attachment 421171 [details] [diff] [review]
many user LDAP auto-complete patch

Aaron, sorry for the delay. The patch works as expected, except for an error message alert on shutdown. This is fixed by forcing a garbage collection on unload. I've added this to the patch and will check in soon.

There were also a few places with tabs instead of spaces, I've also fixed this.

Attachment #421171 - Flags: review?(philipp) → review+
Pushed to comm-central <>
Closed: 13 years ago
Resolution: --- → FIXED
Target Milestone: --- → 1.0b2
You need to log in before you can comment on or make changes to this bug.