Closed
Bug 279640
Opened 20 years ago
Closed 19 years ago
resort order of completion menu of 'To' field.
Categories
(Thunderbird :: Message Compose Window, defect)
Tracking
(Not tracked)
VERIFIED
DUPLICATE
of bug 276632
People
(Reporter: doublehp, Assigned: mscott)
Details
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20050110 Firefox/1.0 (Debian package 1.0+dfsg.1-2)
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20050110 Firefox/1.0 (Debian package 1.0+dfsg.1-2)
when entering an address in the 'To' field of a compose window, a menu appears
to compleet it faster; it looksto me like this menu just pick out the emails in
the address book as is; I d expect TB to sort them in some order.
Reproducible: Always
Expected Results:
I d expect TB to sort emails, for example putting first the email of ppl I most
wrote two for the last 4 weeks ...
maybe I have a far far far away aunt called abcdmmm, and a very cool girl friend
called adcbnnnn I write every day ... why should TB put my girl friend always
after that aunt I dont mind about ? Cant TB understand that if I write my gf
everyday, there is a higher probability I write her tomorrow than that aunt ???
just keep a track of recent pppl I mailed for a given time ( tasts can change),
and resort that menu with those datas.
I tell about aunt and gf, but it could be the same with resailers, boss,
custoremrs, wife, or even my local baker :)
Comment 1•19 years ago
|
||
This is an automated message, with ID "auto-resolve01".
This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.
While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.
If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.
The latest beta releases can be obtained from:
Firefox: http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey: http://www.mozilla.org/projects/seamonkey/
Comment 3•19 years ago
|
||
in 1.5beta 2, we sort by frequency of use, so the addresses you send to more
often will be higher in the list
*** This bug has been marked as a duplicate of 276632 ***
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → DUPLICATE
(In reply to comment #3)
> in 1.5beta 2, we sort by frequency of use, so the addresses you send to more
> often will be higher in the list
>
> *** This bug has been marked as a duplicate of 276632 ***
note that I used to mail a friend about 400 to 500 times in 6 months, 2 years
ago, and no more now.
What happens if I write to people let say once a week for 1 year from now ?
that far less than the 500 for the first one; still, I expect to get the latter
address ...
volum reflects frequency, you you should average that only on ... let say the
last 6 onths ...
Comment 5•19 years ago
|
||
yes, I know. We talked about that issue but decided that what we have now is a
lot better than what we had before. It came down to a choice of either doing
nothing for 1.5, or doing what we did.
Comment 6•18 years ago
|
||
David, should I file a new bug for the timing issue? It sounds reasonable for me because we cannot force the user to recreate the affected address book card.
Status: RESOLVED → VERIFIED
Comment 7•18 years ago
|
||
Henrik, you can file an RFE, and mark it help wanted. Perhaps someone will come up with some improvements.
You need to log in
before you can comment on or make changes to this bug.
Description
•