Attachment 91603 Details for Bug 64520 – Contact_Info_Field_Flag_Read_Only: add

[patch] Contact_Info_Field_Flag_Read_Only: add

0001-Contact_Info_Field_Flag_Read_Only-add.patch (text/plain), 1.63 KB, created by Simon McVittie on 2014-01-07 14:39:48 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Simon McVittie

Created: 2014-01-07 14:39:48 UTC

Size: 1.63 KB

patch

obsolete

>From b0b35d4ebe98e1321c5f9003404fa4bdda255b18 Mon Sep 17 00:00:00 2001
>From: Simon McVittie <simon.mcvittie@collabora.co.uk>
>Date: Tue, 7 Jan 2014 14:37:19 +0000
>Subject: [PATCH] Contact_Info_Field_Flag_Read_Only: add
>
>Bug: https://bugs.freedesktop.org/show_bug.cgi?id=64520
>---
> spec/Connection_Interface_Contact_Info.xml | 17 +++++++++++++++++
> 1 file changed, 17 insertions(+)
>
>diff --git a/spec/Connection_Interface_Contact_Info.xml b/spec/Connection_Interface_Contact_Info.xml
>index 527d325..3865dd9 100644
>--- a/spec/Connection_Interface_Contact_Info.xml
>+++ b/spec/Connection_Interface_Contact_Info.xml
>@@ -500,6 +500,23 @@ Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA.</
> 'fn' field.
> </tp:docstring>
> </tp:flag>
>+
>+ <tp:flag suffix="Read_Only" value="4">
>+ <tp:docstring xmlns="http://www.w3.org/1999/xhtml">
>+ Indicates that this field is read-only in the contact's
>+ own vCard: it might be synthesized by either the server
>+ or the connection manager. For instance, the Google Talk XMPP
>+ server includes each contact's Google Plus URL in their vCard
>+ as a read-only <code>URL</code> field.
>+
>+ User interfaces SHOULD present this field as uneditable, or
>+ hide it entirely.
>+
>+ If a client attempts to edit a read-only field, the result
>+ is undefined. It may appear to succeed (but actually be ignored),
>+ or cause an error.
>+ </tp:docstring>
>+ </tp:flag>
> </tp:flags>
> 
> <tp:docstring xmlns="http://www.w3.org/1999/xhtml">
>-- 
>1.8.5.2
>

Actions: View | Splinter Review

Attachments on bug 64520: 91603

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.