Steps to reproduce: -open Address Book; -open New mail, type one first letter of the name //note: it autocomplete by the first one (in a sort order) and doesn't give you other matches if they are slightly different:" xena, xina,...."
****observed with today's 1999-10-13 win build*****
Sending to ducarroz. We don't have 'real' autocomplete yet, but I was unable to find the feature bug for autocomplete on ducarroz' list. I am changing this to be that feature bug, from "Address Book: no multiple matches are found when autocomplete" So this feature bug is for tracking the entire autocomplete feature for addressing in New Message.
Right now, if you don't enter anything in the To: field at all and press Enter, it autocompletes to the first address in the address book. That doesn't seem right. (Linux build 1999.11.30.08)
The bug that zach mentions was fixed recently by ducarroz.
Note: that when implementing this, we need to search all Personal Address Books for a match. This was brought to my attention and I wanted to make sure that the full functionality includes all books.
This works well enough for B1 (file specific bugs if not). The remaining full-featured implementation can wait until after B1.
*** Bug 18629 has been marked as a duplicate of this bug. ***
Verified/Duplicate bug 18629 states that newly added cards are not recognized until abook has been closed then reopened. This is now part of this bug and should be one of the scenarios tested when this is fixed.
AB has a notion of last modification date. I should check for it to decide if I need to rebuild the autocomplete cache or not. Actually, we build it only once the first time we call Autocomplete. Should be an easy (temporary) fix
J-F, can you outline briefly what functionality should be implemented so far? I get weird pinpoint addressing behavior, but have no way of knowing if it's a bug or just not implemented yet.
The first time we do autocomplete, we cache the first 100 email addresses we found in first the personal AB and then in the collected AB. Auto complete will use only those cached addresses for the whole life of the application. That means: 1) if you have more than 100 addresses, we will not be able to autocomplete againss all of them! 2) all modification done in the AB or new entry added will not be seen by the autocomplete until you restart the app. That includes new collected addresses. 3) other AB than the personal and the collected AB are ignored. Kind of limited!
This should be release-noted, don't you think?
Beginning 3/27 we will focus exclusively on the backend implementation for 2 weeks. At that point, we will re-evaluate and adjust.
move to M16. Not M15 stoppers
Feature checked in. Some part of the autocomplete widget are not finished. The widget doesn support yet a popup menu and still have some problem when theautocomplete result doesn't match directly the user input. See bug 36730 and 36734 for more info and tracking.
The original bug as stated was not implemented, this bug became the tracking bug for implementing it. However, several other scenarios were added to this and are fixed (zach's 11/30 comment and esther's 1/21 comment). #2 & 3 of ducarroz's comment on 2/25 are also fixed. A new bug was opened (36730) to track the implementation of autocomplete or address matching to find all the matches and pop up a list so this bug will be verified. More specific bugs should be logged for the part of this feature that is now implemented.