incubator-callback-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Filip Maj <...@adobe.com>
Subject Re: Unified JS Contact object
Date Mon, 12 Mar 2012 18:56:07 GMT
Let's make the change and I can test it out on Android on my end - just
ping me.

On 3/12/12 10:22 AM, "Becky Gibson" <gibson.becky@gmail.com> wrote:

>The unified JS contact object initializes the contact object incorrectly.
>Base on the June, 2011 and March, 2012 definition for the contact object,
> parameters that are not defined should have the initial value of null:
>
>All Contact <http://w3c-test.org/dap/contacts/#idl-def-Contact> objects *
>must* include all attributes supported by the implementation, regardless
>of
>whether these attributes have been assigned a null value or not. If a
>supported attribute has not been assigned a value by the user or the
>implementation, then this attribute *must* still be present in the
>resulting Contact <http://w3c-test.org/dap/contacts/#idl-def-Contact>
>object
>and *must* have a value of null.
>
>The current implementation initializes all of the array fields to an empty
>array rather than null if no value is provided.   The iOS code relies on
>the distinction between null and empty array during an update of a
>contact.
> If an array value is null, that parameter is ignored (not changed), if it
>is an empty array and data exists, the stored date for that parameter is
>removed.
>
>Not sure if changing this back to the spec will affect the other
>platforms?
>
>-becky


Mime
View raw message