When editing a contact or creating a new one and merging with other suggested contacts already on the device, the merging algorithm should preserve given name and family name of the contact being edited or created.
Sorry Ayman if I bother you with this topic again but we split our previous efforts changing the merge algorithms in several bugs to be more specific and this is here to ask for your blessings ,) This is the behaviour we talked about in Skype so I would appreciate if you can leave a comment saying you agree and why. Thank you.
(In reply to Salvador de la Puente González [:salva] from comment #1) > Sorry Ayman if I bother you with this topic again but we split our previous > efforts changing the merge algorithms in several bugs to be more specific > and this is here to ask for your blessings ,) > > This is the behaviour we talked about in Skype so I would appreciate if you > can leave a comment saying you agree and why. > > Thank you. Your welcome to bother me with the topic all day long Salva - its my job to be bothered by it ;) Yes as discussed over Skype this is a very pragmatic proposal. The theory behind it is that if the user is actively creating a new contact or editing an existing contact the contact that is being created or edited is King. That is to say that it is reasonable to surmise that the created / edited contact is the contact that holds the information that is newer/fresher/more up to date/important to the end user because it is the one being created / updated. In view of this it is this contact whose information should be presented when, upon editing being completed, duplicates found and merge initiated, there is a conflict in the givenName or familyName fields between this contact and the contact that is being merged into it. Lets not forget that there is a safety net in place. The user is presented with the list of contacts that will be merged into the contact that has been created or edited. Therefore they have visibility of the name fields of the proposed contacts to merge and can actively prevent them merging by deselecting them. This has by blessing, now go forth and code in peace Salve :)
Comment on attachment 800001 [details] 11941.html Very nice patch. Thank you!