276327 - Cleaning information in the address book

Status: RESOLVED DUPLICATE of bug 160965

(Thunderbird :: Address Book, defect)

Description

[Kiko Castañer]

If you have an address book with some address cards, you can create a sublist in
the address book.

After that, move some cards into the sublist. You can see them in the addess
book and in the sublist.

finally, delete the address cards from the address book. If you've done that,
you can see that there are some address cards without information (it was the
same card that I've deleted).


I'm expecting one of two possibilities, when i do that:
1. If you delete the card from the address book, then you have to delete the
same card from the sublist.
2. If you delete the card from the address book, you haven't to clean the
information in the card, it has to still be in there.

Comment 1

[OstGote!]

xref Bug 160965, Bug 181165, and bug 152133 

(as I understand it, the codebase is shared, but I'm not sure).

Comment 2

[Mark Banner (:standard8)]

Reporter, your expectations are unclear. 

Assuming that you have a card in an address book and in a sublist (mailing 
list), what do you expect to happen when you delete the card from the address 
book?

Case 1 I think you mean that if you delete the card from the address book it 
should stay in the mailing list.

->This isn't the way the address book works, the mailing lists contain a 
reference to the email address for cards and not the whole card. Hence you 
can't have the card in the mailing list and not the address book. If you want 
prompting before you delete the card, then that is bug 160965.

Case 2 Are you saying here that if you do delete the card from the address 
book, you shouldn't have to delete it from the mailing list as well? If so, 
then that is bug 272999 (thunderbird version).

Please post a comment here letting us know what you want.

Comment 3

[Mark Banner (:standard8)]

No response from reporter for more than a month, resolving as duplicate of bug 
160965 as that seems most appropriate, for the description given.

Reporter, please re-open with exact description of what you are expecting to 
happen if bug 160965 or bug 272999 (272999 is now fixed) don't represent what 
you want.

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