120445 - Multi-select cards, drag-n-drop into list, only 1st address remains

Status: VERIFIED WONTFIX

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

Description

[Ninoschka Baca]

Trunk build 2002-01-16-03: WinMe
Trunk build 2002-01-16-08: Linux RH 7.1

Overview: Select many cards, then perform a Drag-n-drop into a list, close/open 
the list and only the first email displays. 

Steps to reproduce:
1. Open an address book with a variety of cards (i.e. 10)
2. Select the New List button
3. Use the shift key to select multiple cards, then drag-n-drop these cards into 
the list.
4. Close the list
5. Open the list

Actual Results: Only the first email address remains.
Expected Results: All email addresses should appear

Comment 1

[Ninoschka Baca]

Additional Information:

Steps to reproduce:
1. Select the New List button
2. Select 2 cards, then drag-n-drop into the list (these entries appear on 
the 1st line with the 2 addresses separated by commas, addresses 1 and 2)
3. With the list still open, select another set of cards, then drag-n-drop into 
the list (these entries appear on a second line with addresses separated by 
commas, addresses 1 and 3). 
4. Close the list
5. Open the list

Actual Results: Only 2 addresses remain when there should be 4. It appears to 
only save the first address for each drag-n-drop (i.e. it saved addresses 1 and 
3)
Expected Results: All 4 addresses should be present.

Comment 2

[Ninoschka Baca]

nsbeta1 because this is data loss.

Comment 3

[racham]

I couldn't reproduce this using 14th's build (Win XP). I could see all 4
addresses collected as result of 2 separate drag-n-drop events. Let me try with
today's build. It's probably a regerssion.

Comment 4

[Ninoschka Baca]

I showed Bhuvan how this occurs on my systems. Raising severity to major so we
could atleast have a workaround for bug# 42879. 

Comment 5

[(not reading, please use [e-mail] instead)]

wontfix.  this dialog is becoming modal.

Comment 6

[Ninoschka Baca]

Verified Wontfix.

Comment 7

[Ninoschka Baca]

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