974725 - [B2G][NFC] Support different vcard mime types for Contacts

Status: RESOLVED FIXED

(Firefox OS Graveyard :: NFC, defect)

Description

[Garner Lee]

NFC Manager doesn't handle vcard variants: text/x-Vcard, text/x-vcard, etc.

NFC Manager currently only handles the "Well Known" mime-type "text/vcard", but not the other deprecated ones as referenced in:

http://www.ietf.org/rfc/rfc6350.txt, under:

10.1.  Media Type Registration

Android still sends text/x-vCard and text/x-vcard for example over P2P, so some interoperability is desirable.

There are two possible ways to handle this. Contacts app is updated to accept all variants, and NFC manager doesn't try to bridge this gap. Or NFC manager just treats them as special cases (as it does now for text/vcard only), and re-routes it to whatever is registered to handle that type.

Expected:
Decide which way to go, and update any handlers/parsers as needed.

Comment 1

[Ken Chang[:kenkai]]

Garner, I assign this bug to you. If it is wrong assignment, please let me know.

Comment 2

[Garner Lee]

Attachment: [B2G][NFC] Support different vcard mime types for Contacts

Comment 3

[Garner Lee]

NFC manager cannot generically figure what vcard versions the app supports. So, this current change just treats text/vcard, text/x-vcard, text/x-vCard the same. If the application fails to import or handle it, the user can just try again with another contacts-type app with better vcard import support.

UX/Decision feedback is welcome.

Comment 4

[Garner Lee]

Minor: fixed a MozActivity test reference error.

Green: https://travis-ci.org/mozilla-b2g/gaia/builds/21981604

Comment 5

[Ryan VanderMeulen [:RyanVM]]

Master: https://github.com/mozilla-b2g/gaia/commit/3864767928fa40d99e734cfe3dd736aaaa09891f