Autocomplete - primary email address no longer appears before additional email address (now sorted alphabetically)

RESOLVED FIXED in Thunderbird 3.1b2

Status

MailNews Core
Address Book
RESOLVED FIXED
8 years ago
7 years ago

People

(Reporter: standard8, Assigned: standard8)

Tracking

({fixed-seamonkey2.0.4, regression})

Trunk
Thunderbird 3.1b2
fixed-seamonkey2.0.4, regression

Firefox Tracking Flags

(blocking-thunderbird3.1 beta2+, thunderbird3.1 beta2-fixed, blocking-thunderbird3.0 .4+, thunderbird3.0 .4-fixed)

Details

(Whiteboard: [gs], URL)

Attachments

(1 attachment)

(Assignee)

Description

8 years ago
This is a regression from Thunderbird 2.

In Thunderbird 2 for cards that contained both an email address ('primary') and an additional email address, the primary email address would always be listed first.

In Thunderbird 3, primary and additional are sorted alphabetically.


This bug will fix this one clear regression. Please do not suggest other sort orders/options/bugs here, but file them in separate bugs.
(Assignee)

Updated

8 years ago
Duplicate of this bug: 539650
(Assignee)

Updated

8 years ago
blocking-thunderbird3.0: needed → .3+
(Assignee)

Updated

8 years ago
Duplicate of this bug: 532639

Comment 3

8 years ago
Am I seeing correctly that this is planned for TB 3.0.3+ and not 3.0.2?
(Assignee)

Comment 4

8 years ago
(In reply to comment #3)
> Am I seeing correctly that this is planned for TB 3.0.3+ and not 3.0.2?

Yes.

Comment 5

8 years ago
Requesting "blocking1.9.0.18" because the "wanted" items are grayed out.
Flags: blocking1.9.0.18?
(Assignee)

Comment 6

8 years ago
(In reply to comment #5)
> Requesting "blocking1.9.0.18" because the "wanted" items are grayed out.

The fact that it is blocking-thunderbird3.0 is enough of a flag, you don't need wanted as well.
Flags: blocking1.9.0.18?

Comment 7

8 years ago
(In reply to comment #6)
> The fact that it is blocking-thunderbird3.0 is enough of a flag

I thought that flag was outdated because "3.0" is already out the door. Perhaps it should say "3.0.x". Apologies for not reading the "runes" correctly. ;-)

BTW: What does ".3+" mean (after blocking-thunderbird3.0)? Zero point three plus? Partially (a third) blocking? I only knew ?, +, and - as entries.
(Assignee)

Comment 8

8 years ago
(In reply to comment #7)
> BTW: What does ".3+" mean (after blocking-thunderbird3.0)? Zero point three
> plus? Partially (a third) blocking? I only knew ?, +, and - as entries.

See https://wiki.mozilla.org/Thunderbird/Release_Driving/Flags and if you have any more questions please ask on mdat.
(Assignee)

Updated

7 years ago
Duplicate of this bug: 548289

Comment 10

7 years ago
Actually, I would be perfectly happy if the Secondary address got listed first, if and only if *it is the address that I send mail to most frequently*.   In other words, I don't think it makes sense to *always* put the primary address first.   By the same token, it doesn't make sense to sort them alphabetically as appears to be the case now.  Frequency of usage is much more important regardless of Primary or Secondary status.

Comment 11

7 years ago
I still support that the Primary address should be presented first.
I made a decision that this is the default order I wanted, as I added my email addresses to the address book.

I also see that this change will not appear until TB 3.0.3+. :-(

I got fooled into TB 3.0.1 and have returned (with effort)to 2.0.0.23
I'll be cautious before I make that move again!

Comment 12

7 years ago
(In reply to comment #11)
> I still support that the Primary address should be presented first.
> I made a decision that this is the default order I wanted, as I added my email
> addresses to the address book.

Seconded.  The meaning of "primary" is, well... primary.  It shouldn't be sorted below additional unless you have good evidence for doing this.

I'd be OK with having evidence overwhelm the express preference for the primary address, but the assignment of one address as primary /is/ an expressed preference, and I don't think we should run roughshod over it.

Comment 13

7 years ago
(In reply to comment #12)
> I don't think we should run roughshod over it.

Respecting the *frequency* with which the users *actually* use the address is hardly "running roughshod" over their choice (that they made once long ago).

Also, since Thunderbird's address book is so <polite>limited</polite>, perhaps most user's "primary" entry is simply the *first* e-mail they entered for that person.
(Assignee)

Updated

7 years ago
blocking-thunderbird3.0: .3+ → .4+

Comment 14

7 years ago
(In reply to comment #13)
> (In reply to comment #12)
> > I don't think we should run roughshod over it.
> 
> Respecting the *frequency* with which the users *actually* use the address is
> hardly "running roughshod" over their choice (that they made once long ago).
> 
> Also, since Thunderbird's address book is so <polite>limited</polite>, perhaps
> most user's "primary" entry is simply the *first* e-mail they entered for that
> person.

With all due respect, you are misreading me.  After upgrade to TB 3, as far as I can tell, TB is doing nothing with EITHER my expressed preference by means of primary and additional email addresses OR any experience.

All I am getting now is alphabetized completion.  This is, for me, almost always exactly the wrong thing.  Here is what goes wrong:  

1.  I want to send one of my colleagues mail.
2.  My colleague has both a gmail address and an address at my company, whose name begins with "S"
3.  TB gives me the gmail address first (I have it because of google talk), although it is carefully NOT the primary address.
4.  Unless I am careful, information leaks out of my company and into Google, where I don't want it to go.  Also, my colleagues typically use Google just for IM, so they don't see these messages.

I DID think carefully about what address should be primary, and I DO regard ignoring this in favor of alphabetical order as running roughshod over my express preference.

I'm not asking for this to be enshrined forever --- if TB wants to learn from actual behavior, that's fine with me.  It will learn that I obey the primary/additional email distinction and you don't, and we both win.

But if TB is going on no information, I would very much prefer the main email address to be sorted first, instead of having alphabetical order.

Comment 15

7 years ago
I have to agree with Robert Goldman.

I see that this moved from 3.0.3 to 3.0.4. Any reason why it was de-prioritized?

Updated

7 years ago
blocking-thunderbird3.1: --- → rc1+

Comment 16

7 years ago
(In reply to comment #15)
> I see that this moved from 3.0.3 to 3.0.4. Any reason why it was
> de-prioritized?

3.0.3 was already released and had a single (important) bugfix.

Updated

7 years ago
Duplicate of this bug: 552431

Comment 18

7 years ago
Uh, sorry for the dupe, I did try and find if there was another bug out there. I might have depended on Google for that a tad too much.

I too have to agree with Robert Goldman. Voted in favor of solving this bug.

If you need me for testing or development please let me know (although my prime interest is in Java/security/cryptography).
Whiteboard: [gs]
(Assignee)

Comment 19

7 years ago
Created attachment 432916 [details] [diff] [review]
The fix

This should fix the issue. It adapts the sorting algorithm so that it knows about primary and secondary email addresses and takes appropraite action.

Patch includes unit tests for some of the cases I thought of.
Attachment #432916 - Flags: superreview?(bienvenu)
Attachment #432916 - Flags: review?(bienvenu)

Comment 20

7 years ago
Comment on attachment 432916 [details] [diff] [review]
The fix

this works - I had some confusion because my test primary address turned out to be in 3 separate address books, but once I cleared that up, the patch worked fine.
Attachment #432916 - Flags: superreview?(bienvenu)
Attachment #432916 - Flags: superreview+
Attachment #432916 - Flags: review?(bienvenu)
Attachment #432916 - Flags: review+
(Assignee)

Comment 21

7 years ago
Comment on attachment 432916 [details] [diff] [review]
The fix

a=Standard8 for low-medium risk change to code which is well tested with existing unit tests.
Attachment #432916 - Flags: approval-thunderbird3.0.4+
(Assignee)

Comment 22

7 years ago
Checked into all branches:

http://hg.mozilla.org/comm-central/rev/a65be9430322
http://hg.mozilla.org/releases/comm-1.9.1/rev/bbf299382de5
Status: NEW → RESOLVED
blocking-thunderbird3.1: rc1+ → beta2+
Last Resolved: 7 years ago
status-thunderbird3.0: --- → .4-fixed
status-thunderbird3.1: --- → beta2-fixed
Resolution: --- → FIXED
Target Milestone: --- → Thunderbird 3.1b2

Updated

7 years ago
Keywords: fixed-seamonkey2.0.4
You need to log in before you can comment on or make changes to this bug.