WebAPI/ContactsAPI: Difference between revisions

Jump to navigation Jump to search
No edit summary
Line 222: Line 222:
The Firefox for Android implementation of the contacts has a few discrepancies from the specs listed here. They are as follows:
The Firefox for Android implementation of the contacts has a few discrepancies from the specs listed here. They are as follows:


* The `name` field must always be consistent with the `honorificPrefix`, `givenName`, `familyName`, and `honorificSuffix` fields. For example, a contact with the `name` field set to `Dr. John Doe Junior` should have `honorificPrefix` set to `Dr.`, `givenName` set to `John`, etc.
* The "name" field must always be consistent with the "honorificPrefix", "givenName", "familyName", and "honorificSuffix" fields. For example, a contact with the "name" field set to "Dr. John Doe Junior" should have "honorificPrefix" set to "Dr.", "givenName" set to "John", etc.


* The `getRevision()` function is not supported on Android. Calling it will always return an error.
* The "getRevision()" function is not supported on Android. Calling it will always return an error.


* The `updated` and `published` timestamps are not supported on Android. They will always be set to the date `0000-00-00T00:00:00.000Z`.
* The "updated" and "published" timestamps are not supported on Android. They will always be set to the date "0000-00-00T00:00:00.000Z".


* The preferred field for a phone, email, address, etc., if not set to 1, will default to 0 even if the field is omitted completely.
* The preferred field for a phone, email, address, etc., if not set to 1, will default to 0 even if the field is omitted completely.
Confirmed users
120

edits

Navigation menu