Closed Bug 201511 Opened 22 years ago Closed 21 years ago

Autocomplete now puts Collected Addresses before Personal Address Book

Categories

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

defect
Not set
critical

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 158728

People

(Reporter: hacksoncode, Assigned: bugzilla)

References

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4b) Gecko/20030408 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4b) Gecko/20030408 Something changed recently (within the last several weeks) with the order of addresses during autocompletion. I'm now getting addresses that only appear in my Collected Addresses mailbox listed first. It only seems to happen if the collected addresses have realnames in addition to email addresses (e.g. Test 2 <test2@foo.bar>) Reproducible: Always Steps to Reproduce: 1. Create Personal Address Book entry for: "Test 1 <test1@foo.bar>" 2. Send email to "Test 2 <test2@foo.bar>" and "Test 3 <test3@foo.bar>" and verifiy that they went into Collected Addresses. 3. Compose an email and type "test" into the To field. Note: the email addresses might need to actually exist for this to work. I used test addresses at work that I'd rather not list here. I.e. the above are not actual examples, but are respresentative of actual examples. Actual Results: Autocompletion suggests: "Test 2 <test2@foo.bar>" followed by "Test 3 <test3@foo.bar>" and then "Test 1 <test1@foo.bar>". Expected Results: "Test 1" should appear first. My impression is that this happened about the same time as the fix for bug #54035 that caused the Ctrl-Enter failure (bug 198976). Also, the flavor of it is similar to the root cause there (events firing in the wrong order). This is very similar to bug 158728, but it is different in that this only started happening recently, and also that bug is talking about yet a third address book being used after Collected Addresses, but still reports Collected Addresses as being shown *after* the Personal Address Book. I have lost several emails that have gone to the wrong address because I didn't notice this for quite some time (in fact, they went to my wife's cell phone SMS rather than her email address, which was *really* annoying). However, I'm sympathetic if someone doesn't consider this real dataloss and wants to reduce the severity to Major.
Moving to address book instead of composition.
Component: Composition → Address Book
Confirming. This effect occurred independent of the order addresses were entered in Address Book, and also independent of the selection in Prefs - MailNews - Addressing - "Add email addresses to my: (selected book)." Collected Addresses entries were listed before Personal Address Book entries, which were listed before other addressbooks' entries. Alphabetical name of the addressbooks doesn't seem to matter either.
Status: UNCONFIRMED → NEW
Ever confirmed: true
confirmed: linux/x86 20030818. I have Personal, Collected and LDAP; Collected is always listed first.
OS: Windows XP → All
Hardware: PC → All
*** Bug 216457 has been marked as a duplicate of this bug. ***
I think that this is in fact a dupe of bug 158728, despite the "differences" noted in the original report. I think that there is in fact no certain order that these names are displayed in, and it's at least partially dependent on the order in which names were added to the book. See my comment in the referenced bug. Ray Trent, if you think I'm on the right track here, please mark this bug as a duplicate.
Marking as duplicate per comment 5. While I think the root cause might be different (since it started happening long after bug 158728), the effect is the same. Also, I haven't had this problem as egregiously in a while, so I'm guessing it was something somewhat subtle that probably morphed back over time... *** This bug has been marked as a duplicate of 158728 ***
Status: NEW → RESOLVED
Closed: 21 years ago
Resolution: --- → DUPLICATE
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.