Closed Bug 577119 Opened 14 years ago Closed 9 years ago

The "Private Addressbook" is searched last

Categories

(Thunderbird :: Address Book, defect)

x86
Windows XP
defect
Not set
minor

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: vladimir_f, Unassigned)

References

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; ru; rv:1.9.2.6) Gecko/20100625 Firefox/3.6.6
Build Identifier: Not correct search order of recepient in "From" field

The "Private Addressbook" is searched last (after "collected addresses", "google addressbook"), when it is more natural to search it first

Reproducible: Always
Component: General → Address Book
QA Contact: general → address-book
Vladimir, are you sure it isn't giving the most recently used or most used addresses first, regardless of address book?  (which is what I think it should be doing per spec, it should not be not ordered on address book)
See Also: → 1114751
(In reply to Wayne Mery (:wsmwk) from comment #1)
> Vladimir, are you sure it isn't giving the most recently used or most used
> addresses first, regardless of address book?

Yes, at the time this bug was filed, popularityIndex had absolute priority in sorting autocomplete results.
We've added a legitimate exception in Bug 325458: full nickname matches must top everything by design, to fulfil their alias function (like FF keywords).
We've somewhat undermined popularityIndex in Bug 970456 and are getting first feedback that it might have been the wrong road.

But we've never done any weighting based on ABs, as wrongly assumed in comment 0.
So this is technically invalid.

> (which is what I think it
> should be doing per spec, it should not be not ordered on address book)

+1. If we're serious about "frecency" (popularityIndex enhanced by recency and correlating keyboard inputs with results picked), then we cannot take any other stiff criteria above that (bug 1134986).
So this idea has been wontfixed in the past (Bug 64662, bug 158728).
Unfortunately we're discussing it again, bug 1114751.
invalid (/wontfix) per comment 2
Status: UNCONFIRMED → RESOLVED
Closed: 9 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.