Open Bug 1042801 Opened 10 years ago Updated 2 years ago

[ldap_2.servers.*.autoComplete.nameFormat] setting no longer works

Categories

(Thunderbird :: Message Compose Window, defect)

31 Branch
x86_64
Windows 7
defect

Tracking

(thunderbird_esr38+)

Tracking Status
thunderbird_esr38 + ---

People

(Reporter: michal, Unassigned)

References

Details

(Keywords: regression)

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: Configure LDAP address book (source: Microsoft ActiveDirectory) with following setting: ldap_2.servers.MyLDAP.autoComplete.nameFormat = "[givenName] [sn]" Actual results: User displayed as "[cn] <[mail]>" Expected results: User displayed as "[givenName] [sn] <[mail]>" This actually worked before 31.0. Temporary workaround is to set ldap_2.servers.MyCompany.attrmap.DisplayName into some other attribute (eg. [displayName]), but it does not allow Administrator to use more than one attribute (eg. to omit middle names).
Dupe of bug 1050672?
Status: UNCONFIRMED → NEW
Ever confirmed: true
This ticket is about autoComplete.nameFormat attribute, while bug 1050672 relates to autoComplete.commentFormat. When talking about drop-down autocomplete list only, first attribute refers to the first column and latter refers to the second (in certain scenarios). The first attribute (of which this bug is about) has a wider scope of influence though, the outcome of this setting affects eg. mail headers (formatting of recipient name). So it's not exactly a duplicate, though the whole set of features might be affected by single source issue.
Keywords: regression
Let's keep looking at this, but we won't block release on it.
It seems reading those preferences was removed in bug 452232, but which claims the support was just switched over to another framework. I can't say, whether the switch was successful.
Blocks: 452232
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.