284066 - Autocomplete will not add a second or further address

Status: RESOLVED FIXED

(SeaMonkey :: Autocomplete, defect)

Description

[Michael Graubart]

User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8b2) Gecko/20050224
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8b2) Gecko/20050224

In the address pane, when composing mail, autocomplete will enter a full address
from the address book if a nickname or the first few letters of a name are
typed. But if one then wants to enter a second (or further) address on the next
line of the address pane, autocomplete no longer works.

NB: This is specific to the present build of Mozilla. My previous one (a couple
of weeks old) did not show this bug.

Reproducible: Always

Steps to Reproduce:
1. Open 'Compose'.
2. In the address pane, type a nickname or first few letters of name of someone
in your address book.
3. Type paragraph to move insertion point to next line of address pane.
4. Repeat with a different person in your address book.

Actual Results:  
At 2., autocomplete enters full e-address. But at 4., nothing happens.

Expected Results:  
At 4., autocomplete should again have entered the full e-address of the second
person.

eMac G4, OS 10.3.8; Classic theme.

Comment 1

[Michael Graubart]

I have just dowloaded the latest build (2005022610) and this bug is still present.

Comment 2

[Ian Neal]

Tested against Builds 2005022206 and 2005022406 on WinXP and don't see the
problem, so could well be just a Mac OSX problem.

Comment 3

[Michael Graubart]

As far as this being a Mac OS X problem is concerned, I should say, firstly,
that I have just checked it again and have confirmed that the problem really is
there. But, secondly, I should like to emphasize that the problem was not — and
is not, because I have currently gone back to Build 1005021309 and checked —
present in slightly earlier builds than the two in which I detected the bug. So,
OS X or not, something changed in Mozilla between 20050213 and 20050224 that
should not have changed. 

Comment 4

[Stefan [:stefanh]]

Did some testing on Mac OS 10.3.8... Build 2005021509 and erlier are OK, but
build 2005021613 is not OK. So, it looks like a regression from bug 272002. But
it seems that it just happens on the mac? bz, neil -- same problem as bug
282645? Waiting with confirming since it might be a dupe.

Comment 5

[Boris Zbarsky [:bzbarsky]]

Probably dup; worth retesting once the other is fixed.

Comment 6

[Michael Graubart]

Just downloaded Build 2005030210, and the bug has been fixed. Thank you, whoever
did it! I don't feel competent to change 'Resolve bug,……'; someone more
authoritative should do that after more testing.

Comment 7

[Stefan [:stefanh]]

Yes, the patch in bug 282645 seem to have fixed this. Resolving as fixed.