1042766 - Autocomplete clears address input when more than one match found (fixed: caused by LDAP results without required attributes)

Status: RESOLVED INVALID

(Thunderbird :: Message Compose Window, defect)

Description

[Michał Sacharewicz]

Attachment: Screens with bug reproduction

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:30.0) Gecko/20100101 Firefox/30.0 (Beta/Release)
Build ID: 20140605174243

Steps to reproduce:

I have the AutoComplete configured using LDAP-based address book. I've had that configuration running properly since 17.0.4. Everything worked properly until now.

Imagine having following users in LDAP address book:

Andrew Sample
Andrew Example

Case 1 (bugged):
1. Open new compose window
2. Type "Andrew"

Case 2 (proper):
1. Open new compose window
2. Type "Andrew E"



Actual results:

Case 1 (bugged):
After a while (probably the search time) two things happen:
1. The input content *disappears*
2. The dropdown appears with both users

Case 2 (proper):
Dropdown does not appear, but the address gets properly 


Expected results:

Case 1 (bugged):
1. The input content stays as it is
2. The dropdown appears with both users

Case 2 is ok.

Comment 1

[Michał Sacharewicz]

It might be possibly related to bug 486501, bug 443185, if we assume that input is reverting to empty address visible as first on the screen.

This would however mean that something else is terribly wrong, since the config so far worked without showing empty objects:

> lockPref('ldap_2.servers.MyLDAP.autoComplete.filterTemplate', '(|(mail=%v*)(userPrincipalName=%v*)(sn=%v*)(cn=%v*))');

If this preference is not taken into consideration anymore due to bug 529584 fix, it is possible that Autocomplete gathered some more objects from LDAP (even some without distinguishedName) and that's the cause of the issue, though I do not know how to veryfiy it (eg. check the data of the exact object that is being displayed as empty).

Comment 2

[Michał Sacharewicz]

OK, seems writing down a bug helps thinking.

Seems bug 529584 definitely caused that issue. Seems filterTemplate attribute is no longer used and the only filter that is actually taken into account is the general user matching filter in ldap_2.servers.MyLDAP.uri

That parameter was set to '(objectClass=person)' which was definitely matching many unnecessary objects incl. computers without 'distinguishedName'.

After replacing the filter with '(&(objectCategory=Person)(mail=*)(displayName=*))' empty address does not show up, the autocomplete again behaves more or less properly (other issues are mentioned in other bugs).

I will rewrite this bug with more appropriate titile. Issue closed.