| Summary | Don't do lookups on addresses for 1 or 2 characters |
| Queue | IMP |
| Queue Version | HEAD |
| Type | Enhancement |
| State | Resolved |
| Priority | 1. Low |
| Owners | Michael Slusarz <slusarz (at) horde (dot) org> |
| Requester | webadmin (at) ualberta (dot) ca |
| Created | 09/11/2008 (296 days ago) |
| Due | |
| Updated | 12/19/2008 (197 days ago) |
| Assigned | 09/18/2008 (289 days ago) |
| Resolved | 12/19/2008 (197 days ago) |
| Attachments | ContactAutoCompleter.php.patch ![]() |
| Milestone | |
| Patch | Yes |
Taken from
Assigned to Michael Slusarz
State ⇒ Resolved
Unless we want to choose 3 characters for all installations, this
should probably be implemented as a config setting for IMP.
if the addressbook contains less than 200 entries, this entire address
book is sent to the browser and the browser does the search entirely
within browser-space. In this situation, there should be no
limitation on the number of characters so the config text needs to
make this clear.
Patch ⇒ 1
State ⇒ Assigned
New Attachment: ContactAutoCompleter.php.patch
Unless we want to choose 3 characters for all installations, this
should probably be implemented as a config setting for IMP.
State ⇒ Accepted
Version ⇒ HEAD
Queue ⇒ IMP
Patch ⇒
Milestone ⇒
Summary ⇒ Don't do lookups on addresses for 1 or 2 characters
Queue ⇒ Turba
Type ⇒ Enhancement
Priority ⇒ 1. Low
State ⇒ New
addressbooks defined in Turba horde will attempt to do address
completion when you start typing in the "to" field. However, if you
have a large LDAP or other directory server included in the list it
will return enormous lists when you match on one or two characters.
To compound the problem, LDAP will return results based not only on
the starting character of the address but if that character appears at
all in the address so typing an 'a' to start an address will return
everything from alansmith to zumberaya.
I would suggest holding back on any searches for address completion
until the user has typed in at least 3 characters.