Using the 11/19 trunk build I'm getting what I believe to be poor autcomplete results on NT. If I have in my address books: sddd sbbb <firstname.lastname@example.org> Gzzz s <email@example.com> When I type "sddd sb" into the addressing widget it completes to "Gzzz s". I would expect it to complete to "sddd sbbb" since it appears to me to be a closer match.
So, I don't have time to come up with fake results for this other case I saw. I typed in "robinf" which exists as an email address in my collected AB and got back Rob Jaworski which exists as a dislay name. I almost missent the email because of this.
Here are some other problems I see. I don't know the pattern. These are the addresses in my collected address book: Lisa Chiang (display name) firstname.lastname@example.org (I made this address up since I use this for personal stuff and don't want spam to this.) Lisa Chiang (display name) email@example.com Lisa Chiang (display name) firstname.lastname@example.org (no display name) email@example.com When I type: lisa-s, into the addressing field, I do not get matched to lisa-staff. I get a match to firstname.lastname@example.org. I have other examples if you need them.
*** Bug 107921 has been marked as a duplicate of this bug. ***
here is my comments from the dup'ed bug. "If I try to autocomplete 'sures', one of the entry in autocomplete popup shows 'Sean Su <email@example.com>'. "
I realize this isn't perf work, but I'd like to consider this one of those bugs that makes it hard to use mail. Autocomplete pretty much never does the right thing for me anymore. If there's some quick fix that can be implemented before or during the 0.9.6 closure then it would be great if it can be fixed then. If not then please move into 0.9.7
Priority: -- → P1
Summary: Unexpected autcomplete results → Unexpected autocomplete results
Target Milestone: --- → mozilla0.9.6
Status: NEW → ASSIGNED
this should be 097. 096 closes tonight! And this is not an 096 stopper IMHO.
I can move it to 0.9.7, but do you know how many times I've almost sent to the wrong email address! I bet it autocompletes incorrectly more than 50% of the time.
My guess is that the work Alecf did when converting nsCRT::Strncmp to Convert cause this regression (see bug 100214)
I should be able to fix it by tonight...
the problem is that we also match any entries that have short prefixes which share the same first letters as what someone typed. i.e. if I type "Fred" I will also match "F Jones" and "Fr Smith" talked with jean-francois on the phone, and explained how I broke it :)
Alec, can you review the patch? Thanks.
Whiteboard: have fix
Comment on attachment 56784 [details] [diff] [review] proposed fix, v1 sr=alecf
Attachment #56784 - Flags: superreview+
Comment on attachment 56784 [details] [diff] [review] proposed fix, v1 r=varada
Attachment #56784 - Flags: review+
Fixed and checked in.
Status: ASSIGNED → RESOLVED
Last Resolved: 18 years ago
Resolution: --- → FIXED
Whiteboard: have fix
Trunk build 2001-11-09: WinMe, Linux RH 7.1, Mac 9.1 Verified Fixed. I tried all scenarios that were mentioned.
Status: RESOLVED → VERIFIED
*** Bug 107808 has been marked as a duplicate of this bug. ***
You need to log in before you can comment on or make changes to this bug.