From 781afb2c15cdb1e8562232c1d77143352aab5850 Mon Sep 17 00:00:00 2001 From: Jonathon Jongsma Date: Tue, 5 Oct 2010 11:55:52 -0500 Subject: [PATCH] ContactInfo: Add flag for fields that are overwritten by nickname It's likely that clients will want to expose the user's nickname and their contact info in the same place for editing. Howevever, many CMs map one of the ContactInfo fields to the user's nickname, so editing these two fields independantly at the same time results in surprising behavior. Adding a flag to the ContactInfo field will allow clients to hide these duplicate fields when presenting them together. Fixes: fd.o#30631 --- spec/Connection_Interface_Contact_Info.xml | 18 ++++++++++++++++++ 1 files changed, 18 insertions(+), 0 deletions(-) diff --git a/spec/Connection_Interface_Contact_Info.xml b/spec/Connection_Interface_Contact_Info.xml index ce77a56..42881c4 100644 --- a/spec/Connection_Interface_Contact_Info.xml +++ b/spec/Connection_Interface_Contact_Info.xml @@ -470,6 +470,24 @@ Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA. + + + + Indicates that this field will be overwritten when the user's alias is changed with SetAliases + or when the Account's Nickname + is updated. Because of this, clients that allow the editing of the + Alias and the ContactInfo in the same location should hide this field. + + If a client allowed the user to edit both the nickname and the + ContactInfo field together, the user could set them to two different + values even though they map to the same property. This would result + in surprising behavior where the second value would win over the + first. + + + -- 1.7.1