81961 - LDAP autocomplete display odd when pretty name not found

Status: VERIFIED FIXED

(MailNews Core :: LDAP Integration, defect)

Description

[Dan Mosedale (:dmosedale, :dmose)]

from nsILDAPAutoCompleteSession.idl:
 
     * A template string for formatting the autocompletion results.   
     *
     * Required attributes are delimited by curly braces, and optional 
     * attributes are determined by brackets.  Backslash escapes any 
     * character, including itself.  The default template is
     * "[cn] <{mail}>", without the quotes.  This will generate autocomplete
     * items of the form "John Doe <[e-mail]>", or, if the cn is not
     * found, " <[e-mail]>".  This latter form is suboptimal, in that
     * the space and angle brackets are a bit ugly, but should work. 
 
The above-mentioned ugliness should go away.  Either there could be some 
special-case coding for the default (ick!), the syntax could be made more
complex to allow for parts of the template to be conditionalized based on
whether specific attrs are found, or an outputFormatter attribute could be
added, which would be a JS function that would do whatever formatting logic desired.

Comment 1

[Dan Mosedale (:dmosedale, :dmose)]

This was fixed for mail-format addresses when nsIAbLDAPAutoCompFormatter was
factored out of nsILDAPAutoCompleteSession.

Comment 2

[yulian chang]

Yulian Chang wrote:
Dan,
I tried to add an entry without CN in my LDAP server, bologna to test this fix.
But CN is required field to create the entry. What else I can do? Or do you have
any entry without CN? If yes, please give me the server information and the entry.
Thank you for help.

I suspect you're right, and that it's not even possible to have an entry without
a cn.  So I wouldn't worry about it.

Dan

Comment 3

[yulian chang]

Verified.