Closed Bug 18629 Opened 21 years ago Closed 20 years ago

[PP]New Cards added to Address books are not seen when doing Autocomplete


(SeaMonkey :: MailNews: Address Book & Contacts, defect, P3)

Mac System 8.5


(Not tracked)



(Reporter: esther, Assigned: hangas)


(Keywords: platform-parity)

Using build 1999111011M11 on Mac only, if you add a new card to your Personal
Address Book or click on a message that adds a new card to your "Collected
Addressses" book, these cards are not seen when doing an Autocomplete in a
Compose window in the same session.  If you add these cards then close the app,
they are seen when doing an autocomplete.

1. Launch Messenger
2. Open the Address book and add a unique card to your Personal Address Book
(one will not partially or fully match a card in your current Personal Address
book or History book and does not end in, (i.e. Name=xzt and
e-mail = hopefully you don't have this card already in your
Abook!  OK the card and check to see that it is listed in the right pane of the
address book when the Personal Address Book is selected.
3. Close the Address book
4. Click New Ms, in the To: field type in xzt then press <enter>

Result: the To: line autocompletes with
Expected: the autocomplete of the unique name in your Personal Address book (xzt
<> on the To: line

Note: if you close the app then repeat 1 & 4 the name will auto complete as
Also note: the same happens to the Collected Addresses abook if you have added a
unique new name then try to autocomplete before closing app.
QA Contact: lchiang → esther
Esther, can you add a note in the tracking bug for M11 release notes for this?
Target Milestone: M12
JF: any ideas here?  I will take this bug for now, but I cannot imagine what
would be causing it.
Totally normal, the TEMPORARY autocomplete code cache the whole AB content the first time is invoked. Therefore
new AB entries won't be accessible.

Paul, we need to figure a patch. I need somehow to know if the content of the AB is different than last time I cache
it, then I would be able to reset the cache. We need a cache for speed issue... Maybe you can keep a "content version"
number  that you  increase each time the content change.
Added to M11 release notes 11/12/99
Mass move to M13.
Let's not spend any more time than necessary on the temporary autocomplete code.
JF has the bug for the real implementation of autocomplete.
Should we close this bug?
Target Milestone: M13 → M14
Moving to M14.
Keywords: pp
Yes, I think we should close this. Marking a dup of the real autocomplete
feature bug.

*** This bug has been marked as a duplicate of 16354 ***
Closed: 20 years ago
Resolution: --- → DUPLICATE
Verified as dup
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.