Intent to Ship: Contacts API
Rayan Kanso
Contact emails
fin...@chromium.org, natt...@chromium.org, pe...@chromium.org, raya...@chromium.org
Explainer
https://github.com/wicg/contact-api/
Spec
https://wicg.github.io/contact-api/spec/
Tag Review: https://github.com/w3ctag/design-reviews/issues/337
Summary
Allows websites to request the names, e-mail addresses, and/or phone numbers of the contacts available on the user's device. Doing so requires a user gesture, upon which the user must explicitly select information about which contacts are to be shared.
This data is not shared directly. Instead, a contact picker will be shown to the user where they have to select which, if any, data to share with the website. The picker is attributed to the origin, and we visually indicate the data that is to be shared. This flow must be repeated each time the website wants access to contact information: no persistent access is granted.
This launch will not include a “Select All” button in the picker due to privacy abuse concerns around the feature. This might be re-examined in the future depending on how our metrics show users interacting with the picker, but that is unrelated to this launch.
The Origin Trial feedback was positive, with lots of the signed up parties emphasizing the ease of using/integrating with this API, and how they’d like to continue using it in the future.
Link to “Intent to Implement” blink-dev discussion
https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/GBgoS_eCmzM/
Is this feature supported on all six Blink platforms (Windows, Mac, Linux, Chrome OS, Android, and Android WebView)?
No. The feature and solution are platform agnostic, but we only provide an implementation for Android for now, where the problem is significantly more severe than on other platforms. Additional feedback is necessary to understand what the right solution is for the other platforms (e.g. Chrome OS), given that there may not always be a device-canonical contact source available.
Demo link
https://tests.peter.sh/contact-api
Risks
Interoperability and Compatibility
Edge: Positive
Firefox: No resolved position, but positive signals
Safari: No Signals
Web / Framework developers: Positive based on OT feedback
Ergonomics
No adverse effects on Chrome performance are expected. There are plans to start an M80 origin trial simultaneously with the launch to allow developers to request addresses & icons.
Activation
The API can be used immediately when shipped.
Is this feature fully tested by web-platform-tests? Link to test suite results from wpt.fyi.
Yes, link here.
Entry on the feature dashboard
Yoav Weiss
Contact emails
fin...@chromium.org, natt...@chromium.org, pe...@chromium.org, raya...@chromium.org
Explainer
https://github.com/wicg/contact-api/
Spec
https://wicg.github.io/contact-api/spec/
Tag Review: https://github.com/w3ctag/design-reviews/issues/337
Summary
Allows websites to request the names, e-mail addresses, and/or phone numbers of the contacts available on the user's device. Doing so requires a user gesture, upon which the user must explicitly select information about which contacts are to be shared.
This data is not shared directly. Instead, a contact picker will be shown to the user where they have to select which, if any, data to share with the website. The picker is attributed to the origin, and we visually indicate the data that is to be shared. This flow must be repeated each time the website wants access to contact information: no persistent access is granted.
This launch will not include a “Select All” button in the picker due to privacy abuse concerns around the feature. This might be re-examined in the future depending on how our metrics show users interacting with the picker, but that is unrelated to this launch.
The Origin Trial feedback was positive, with lots of the signed up parties emphasizing the ease of using/integrating with this API, and how they’d like to continue using it in the future.
Link to “Intent to Implement” blink-dev discussion
https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/GBgoS_eCmzM/
Is this feature supported on all six Blink platforms (Windows, Mac, Linux, Chrome OS, Android, and Android WebView)?
No. The feature and solution are platform agnostic, but we only provide an implementation for Android for now, where the problem is significantly more severe than on other platforms. Additional feedback is necessary to understand what the right solution is for the other platforms (e.g. Chrome OS), given that there may not always be a device-canonical contact source available.
Demo link
https://tests.peter.sh/contact-api
Risks
Interoperability and Compatibility
Edge: Positive
Firefox: No resolved position, but positive signals
Safari: No Signals
Web / Framework developers: Positive based on OT feedback
Ergonomics
No adverse effects on Chrome performance are expected. There are plans to start an M80 origin trial simultaneously with the launch to allow developers to request addresses & icons.
Activation
The API can be used immediately when shipped.
Is this feature fully tested by web-platform-tests? Link to test suite results from wpt.fyi.
Yes, link here.
Entry on the feature dashboard
--
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAAe2mZ2KBAGy6DxmSYWtDoP7OqEATC1qa-dfg2a%2B0ZCwDaeJEQ%40mail.gmail.com.
Rayan Kanso
Yoav Weiss
Rayan Kanso
Chris Harrelson
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAAe2mZ2cfitrGo%2BgtiELXp7f3F6MvMmQ95c81yZdNy1xJA0GPQ%40mail.gmail.com.
Yoav Weiss
Mike West
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CACj%3DBEieL1c4pkN7NNYeesvevSf1YdHjhpDKbJ91LE_kHwcjcQ%40mail.gmail.com.