101145 - display name not generated from first and last names in new address card

Status: VERIFIED DUPLICATE of bug 99391

(SeaMonkey :: MailNews: Address Book & Contacts, defect)

Description

[Leston Buell]

Previously, if you created a new address card, a new display name would be
generated dynamically as you typed in a first name and a last name. This no
longer happens. To reproduce:

1. Open a new address card.
2. Type in a first name and last name. 
   Note that no display name appears in the display name text field.
3. Type in an e-mail address in the appropriate field.
4. Click OK.
5. Observe that the new address card added to the address book has 
   an e-mail address but lacks a display name.

Expected behaviour:
   1. A display name should be generated dynamically 
      in the display name text field of the address card 
      as the first and last names are typed in.
   2. A display name should be associated with the card and 
      appear in the address card pane of the address book.

I'm using Linux build 2001-09-18-06.

Comment 1

[John Marmion]

I can also verify that this is happening.

The "top.GenerateDisplayName()" function should be activated on input into
LastName or FirstName text fields. But this function is not found. The code
works correctly if the "GenerateDisplayName()" is called without the "top.".
This is also true for the "DisplayNameChanged()" which is bug 99391. This bug is
thus a duplicate of 99391. This simple change would fix it but I don't know what
has happened to cause this.

Comment 2

[Ninoschka Baca]

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

Comment 3

[marina]

Ninoshka, i don't think that we have to mark bug # 99391 as a dup of this one.
The case reported here is not happening on Windows and might be Linux specific,
what i described in 99391 is a generic bug for all platforms. If any changes
this one is a subcase of 99391

Comment 4

[John Marmion]

I see this behaviour on windows and linux. I have posted a patch for bug 99391
which fixes this bug also. I did post a solution to this a number of days ago
but nobody picked up on it. The patch is a very simple fix. Perhaps someone more
experienced in XUL might explain this behaviour.

Comment 5

[Scott MacGregor]

dup'ing.

*** This bug has been marked as a duplicate of 99391 ***

Comment 6

[Ninoschka Baca]

Verified Duplicate.