Actually, I just tried this and wasn't able to reproduce the worst 
stuff, which was showing the dropdown for non-matched addresses. So 
I'm willing to resolve this.

Having looked at this a bit over the last few months, the unfortunate 
reality is to do much of what is asked would probably require us to 
ditch the scriptaculous JS code and create a new JS library ourselves 
(which would not be a trivial undertaking) or, at the least, have to 
rewrite large portions of the scriptaculous code (i.e. no more using 
the public API).

Also see the behavior described in bug 5544.

Set an IMP 4.2 milestone on this

Some tweaks to the new autocomplete code (could probably be applied to 
DIMP as well)



1. If there is only one match for an address fragment, expand it 
without user intervention. In other words, if I type a unique name 
fragment (like, say, my wife's name ;) into an address field and 
immediately tab out of it, it should be automatically expanded without 
a dropdown, like the old auto-expand behavior. Same thing for if I 
type several unique names seperated by commas - I shouldn't have to 
pause to complete each one if there's only one choice.



2. Don't show the dropdown if there's just one choice, period - just 
expand, perhaps highlighting the filled-in text so it's easy to 
correct if it was wrong. Not 100% sure on this one.



3. Don't show a dropdown when the address is already complete. Right 
now I can get the dropdown to show if I fiddle around in a field 
that's already expanded - before we didn't muck with already valid 
addresses, this should be the same (especially since a name + email 
pair is not going to provide multiple options anyway - another 
instance of showing dropdowns with just one option).