65201 - @defaultdomain autocomplete should be last item

Status: VERIFIED WONTFIX

(MailNews Core :: Composition, defect)

Description

[Brian Z]

When entering a name (so Mozilla will autocomplete the address), the @default
domain should be displayed last when other entries are found.  Why would I want
to use the last resort type entry first?  Thanks!

Comment 1

[Keyser Sose]

Marking NEW, although i think this is the wrong place but not sure so just
marking it NEW.

Comment 2

[Brian Z]

I was wondering that too.  This was my best guess because the popup dialog is in
the composition window.  One thing, are you sure this is an enhancement?  I tend
to think this is more of a bug because if multiple entries are found, why would
my first choice be the last resort entry ((textentered)@mydomain)?  Just my
oppinion though, you are the expert. :)  Thanks & Keep up the good work!

Comment 3

[[e-mail] (gone - use [e-mail] instead)]

I agree, this is annoying.  My brother has an @earthlink.net address, and it 
always tries to autocomplete to the @netscape.com domain, when in fact it is *I* 
who work for Netscape, not him ;-) (Gloat, gloat).

Comment 4

[Ben Bucksch (:BenB)]

severity: enhanced -> minor, because it just makes no sense to list the
defaultdomain first.

Comment 5

[Brian Z]

Nominating mozilla0.9.  It is a pain, wouldn't bee too hard to fix (correct me
if I'm worng), and it shouldn't be present in the next vendor branch.

Comment 6

[Andrew Taylor]

Attachment: Moves @defaultdomain completions to the end of the list

Comment 7

[Jean-Francois Ducarroz]

*** Bug 68188 has been marked as a duplicate of this bug. ***

Comment 8

[Brian Z]

nominating mozilla0.9.1.  could we have review on the patch?

Comment 9

[Brian Z]

adding review keyword

Comment 10

[Jean-Francois Ducarroz]

German, what do you think about moving the default result to the end of the
autocompletion list?

Personnaly I don't think is the right stuff to do, especially is the list is long!

Comment 11

[jglick]

I think entries in the users local address books should come before the @domain 
address since matches from a local ab are a more likely match.

Potential matchs from an LDAP directory could come after the @domain address.

Comment 12

[Ben Bucksch (:BenB)]

> Potential matchs from an LDAP directory could come after the @domain address.

I disagree. Reasons:
- My personal address book (in the general meaning) might lie on an LDAP server.
My "Personal Address Book" (in Mozilla) will be empty in this case.
- Organizations with an LDAP server will probably have all users in that
database and you won't need the default domain (which is for organizations, I
assume).
- Autocompletion against public, general LDAP servers on the internet is IMO a
bad idea.

Comment 13

[jglick]

>My personal address book (in the general meaning) might lie on an LDAP server.
True. OK, scratch the last part of my comment. I agree the @domain default 
should be the last item for the reasons people have stated above.

ducarroz, why do you think it should be the first item?

Comment 14

[Jean-Francois Ducarroz]

the main reason is to match what we do in 4.x. If the user is trying to send a
message to scott@<default domain> and just type scott, we will probably have
several other scott something matches. In the case we don't have THE scott in
the Addressbook, the primary choose would be to accept the user input. Let try
this way: The user is always right, therefore we must trust him first, then
politly proposed other choose...

Comment 15

[Ben Bucksch (:BenB)]

> The user is always right, therefore we must trust him first, then
> politly proposed other choose...

When I type "ducarroz", I don't say or mean <[e-mail]>, but the
ducarroz in my address book. In a way, the ducarroz in my address book is what I
said. (I assume non-existance of the Collected Addressbook, which I consider a
bad idea for exactly that reason.)

Comment 16

[Jean-Francois Ducarroz]

in 4.x, you will have:

ducarroz@<default domain>
[e-mail]

the second ducarroz will be pre-selected and prefill! The problem of putting the
at default domain last is that in case you have a lot of matches, it will be
lost at the end.

Comment 17

[Brian Z]

guess we missed 0.9.1, moving to 0.9.2.  Can anbybody review, we have a patch.  
Thanks!

Comment 18

[Jean-Francois Ducarroz]

sorry but I still disagree. The @default domain should be in first position like
in 4.x.

Comment 19

[jglick]

>in 4.x, you will have:
>ducarroz@<default domain>
>[e-mail]

>the second ducarroz will be pre-selected and prefill! The problem of putting 
>the at default domain last is that in case you have a lot of matches, it will 
>be lost at the end.

I agree with ducarroz for the reasons he states above.  

Comment 20

[Ben Bucksch (:BenB)]

The problem is that in the home user setup, the default domain is useless. The
domain is that of the ISP, and the likelyness that the ISP of the correspondants
match is very small.

It only makes sense if all of the following is true:
- a middle- to big-size company, where people frequently mail each other
  internally
- the user typed the recipient's username completely (!)
That makes it useful only in very few cases.

Comment 21

[Brian Z]

Is it possible this could be an option for the end user?

Comment 22

[Brian Z]

Just noticed in 0.9.2 that you can now scroll through entries.  I think that 
makse my bug resolved. :)  I'm happy with things.  Thanks guys!

Comment 23

[[e-mail] (gone - use [e-mail] instead)]

verified per reporter's comments.