Closed Bug 116006 Opened 24 years ago Closed 15 years ago

should be able to designate primary auto-complete addr

Categories

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

x86
Windows 2000
enhancement
Not set
normal

Tracking

(Not tracked)

RESOLVED EXPIRED

People

(Reporter: jud, Unassigned)

Details

This may actually be a mail compose FE bug, but, there's some abook backend work that would have to be done anyway. problem: I run into the case where auto-collect sucks in many addrs that look alike (joe@main-server.com, joe@phone.com, joe@foo-server.com). I should be able to designate which one I want to be the primary auto-complete addr, otherwise, I'm constantly having to manually select which addr I actually want. I suppose the definition of "primary" here is based on the auto-complete search algorithm. I'm asking for sort based primary designation, not, addr book card entry based primary designation. There are several bugs filed requesting enhancements to the auto-collection and auto-completion of abook entries. Perhaps the design semantics should be re-visited.?
this is a good idea. I've filed some of these bugs myself. I think we'll need to revisit some of these next time.
Assignee: racham → ducarroz
Target Milestone: --- → mozilla1.2
Status: NEW → ASSIGNED
Product: Browser → Seamonkey
Assignee: ducarroz → mail
Status: ASSIGNED → NEW
QA Contact: nbaca → addressbook
Target Milestone: mozilla1.2alpha → ---
MASS-CHANGE: This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state. If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way. If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar). If no action happens within the next few months, we move this bug report to an EXPIRED state. Query tag for this change: mass-UNCONFIRM-20090614
Status: NEW → UNCONFIRMED
MASS-CHANGE: This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago. Because of this, we're resolving the bug as EXPIRED. If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component. Query tag for this change: EXPIRED-20100420
Status: UNCONFIRMED → RESOLVED
Closed: 15 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.