271439 - autocomplete selects wrong address

Status: RESOLVED WORKSFORME

(Thunderbird :: Message Compose Window, defect)

Description

[Terry Bradshaw]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0

When using autocomplete in the address field in a composition window, incorrect
addresses will be selected, even if you explictly type in an address.

Reproducible: Always
Steps to Reproduce:
1. Open a composition window.
2. Type the first few letters of the address, wait for autocomplete to come up.
The bugs occurs with when autocomplete finds multiple matches.
3. Now complete the address, not selecting any of the pulldown addresses, typing
something other than what was listed in the autocomplete, quickly, and hit
enter. Example: ter<PAUSE,AUTOCOMPLETE COMES UP WITH MULTIPLE CHOICES>,
[e-mail]<ENTER>
4. Autocomplete will select the first address from the pulldown, even though you
have selected nothing and typed in a full address.

Actual Results:  
Once started, autoselect will always select an address, even if one is not selected.

Expected Results:  
The autocomplete should not select the first address in the pulldown unless it
was selected.

Comment 1

[Mike Cowperthwaite]

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

Comment 2

[Mike Cowperthwaite]

This is fairly simple to reproduce, you just have to type that final part of the 
address quickly and <enter> or <tab> before the list closes.

Reproduced with TB 0.9+1126, Win2K.  Updating platform.
I don't see this behavior with Moz 1.8a5.

(In reply to comment #0)
> Actual Results:  
> Once started, autoselect will always select an address, even if one is
> not selected.

I don't see this part -- as noted in the dupe, if you type a complete address 
which doesn't match anything, but then wait for the dropdown to close, then what 
you type will be selected.

Comment 3

[Giacomo Catenazzi]

I'm able to reproduce it, with thunderbird 1.0, and I confirm #0.
Example:

write in To: line: "mozilla.org",
delete "@mydomain.tdl"
then go to the beginning of the line and add "abuse@".
You see "[e-mail]"
If you move away this line, thunderbird will rewrite the address to
"[e-mail]".

Comment 4

[david.dieterich]

This is an important one to fix.  It's easy to send an email to the wrong person
or group. It is frustrating to try and try to get the correct address to take
when TB wants the first match.
My testcase is this:
1. Type David on the 'To' line.
>>> My default address pops up.  About 10 other David's are in the dropdown list
2. Select another David.
>>> Sometimes it selects the correct, sometimes not. It seems that I get lucky
about 40% of the time. Sometimes I have to try 4 or 5 times to get it right.

Comment 5

[Mike Cowperthwaite]

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

Comment 6

[Mike Cowperthwaite]

This bug was opened just after bug 265509 was allegedly fixed.  Problem still 
exists in 1.0, tho.  (I can't check trunk builds at the moment, since the 0225 
trunk has problems opening a compose window.)

Comment 7

[Mike Cowperthwaite]

OK -- this does appear to be fixed in trunk builds (+0222).
Unfortunately, I can't request blocking on 1.0.1.

Comment 8

[david.dieterich]

Verified that this bug was fixed within the last 2.5 weeks as the operation
works reliably in today's trunk build 0228, but not in 0210.

Comment 9

[Mike Cowperthwaite]

Clearing the request flag -- TB 1.1 will be from the current trunk.

=>WFM (since I don't know where the fix was done).

Terry Bradshaw, if you find this problem is still an issue with a current 
nightly build (or with future releases) feel free to reopen this bug.

Comment 10

[david.dieterich]

This bug needs to be reopened and I do not have this ability.  I stated after a
day of use that it worked fine... and it does for new messages.  However, it
still doesn't work reliably for forwarded messages. I'm using a trunk build with
Help About = "version 1.0+ (20050228)".
In addition a new regression was introduced. Autocomplete doesn't work at all
when replying. 

Comment 11

[david.dieterich]

The other related regression is that the next To: line steals the cursor back
from the message body window while composing an email sometimes.
Steps to Reproduce:
1. Forward a message to two people
2. Type in the message body
>>> See the cursor jump up to the 3rd To: line and see the last bit of your
message body on the To: line.  
Both these autocomplete regressions need fixing prior to the next release.

Comment 12

[Mike Cowperthwaite]

(In reply to comment #10)
> it still doesn't work reliably for forwarded messages.

This makes no sense at all.  Even if it is true, that sounds like it would be a 
new bug, not this same bug reopened.  Before I spend any time attempting to 
confirm this problem:

Forward INLINE or AS ATTACHMENT?
Compose as HTML or PLAIN?
What about the REPLY case, is that broken also?
When you forward a message and it fails, is the From: line initialized to the 
same identity (assuming you have multiple accounts or identities) as when you 
create a new message?

Comment 13

[david.dieterich]

As requested: With version 1.0+ (20050307), autocomplete selects the correct
address:
 1. Reliably with a new message
 2. Intermittently when Forwarding a message 
 3. Intermittently when Replying to a message
Answers:
Forward INLINE or AS ATTACHMENT?
 Inline. Same behavior with As Attachment.
Compose as HTML or PLAIN?
 HTML. Send as Both.
What about the REPLY case, is that broken also?
 Yes.
When you forward a message and it fails, is the From: line initialized to the 
same identity (assuming you have multiple accounts or identities) as when you 
create a new message?
 N/A. One account.