Closed
Bug 837893
Opened 12 years ago
Closed 11 years ago
[CONTACTS][FACEBOOK] Duplicate contact vanishing from contact list when user links one of the contacts that is duplicated.
Categories
(Firefox OS Graveyard :: Gaia::Contacts, defect)
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: maat, Unassigned)
Details
(Whiteboard: interaction [UX-P1], [TEF_REQ])
**DESCRIPTION**
Duplicate contact vanishing from contact list when user links one of the contacts that is duplicated.
**PATH**
1) create a contact with the same first name and last name as a friend in your Facebook friends list
2) navigate to the contact list
3) select the settings icon
4) select Facebook not enables yet
5) log into Facebook
6) select all contacts to be imported
7) select import
8) once import is complete view the contact list and note that contact created in step 1) does not have Facebook information appended to, a separate duplicate contact is created that holds the Facebook information
9) navigate to the contact detail card of the contact created in step 1)
10) select the 'link contact' CTA and link the contact to the Facebook friend with the same name
11) navigate to to the contact list
**EXPECTED**
there will be two contacts with the same name in the contact list as observed in step 8)
**ACTUAL**
only one contact can now be seen in the contact list. the duplicate contact has vanished.
Reporter | ||
Updated•12 years ago
|
Whiteboard: interaction [UX-P1], [TEF_REQ]
Comment 1•12 years ago
|
||
this is not a bug, it is the agreed expected behavior.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → WORKSFORME
Reporter | ||
Comment 2•12 years ago
|
||
(In reply to Jose M. Cantera from comment #1)
> this is not a bug, it is the agreed expected behavior.
This is a bug as the current implementation is certainly not expected behavior. From a UX PoV the system should *always* inform the user that a contact is being automatically removed. the silent removal of a contact from a end users perspective will be interpreted as a system malfunction.. which obviously undermines their perception of the integrity of the system.
Status: RESOLVED → REOPENED
Resolution: WORKSFORME → ---
Comment 3•11 years ago
|
||
the behavior is conformant with the current specification.
Status: REOPENED → RESOLVED
Closed: 12 years ago → 11 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•