Intent to Experiment: Contacts API Address/Icon support

84 views
Skip to first unread message

Rayan Kanso

unread,
Nov 15, 2019, 2:25:08 PM11/15/19
to blink-dev

Contact emails

fin...@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

Extends the Contacts API to allow developers to request contact addresses and icons as well.


Link to “Intent to Prototype” blink-dev discussion

https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/GBgoS_eCmzM/


Goals for experimentation

Is the address/icon information made available through the API sufficient to satisfy developer use-cases?

Specifically when sharing addresses, all available address information is stored in the addressLine attribute, but the broken down address attributes (postalCode, city, country, etc) are sometimes not available and left empty.


Experimental timeline

M80-M82


Any risks when the experiment finishes?

No, the shared information is one-off, users can choose not to share the information while it’s enabled, and there is an API for checking the supported contact properties.


Ongoing technical constraints

None


Will this feature be supported on all five Blink platforms supported by Origin Trials (Windows, Mac, Linux, Chrome OS, and Android)?

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.


Link to entry on the feature dashboard

https://www.chromestatus.com/feature/6511327140904960


Yoav Weiss

unread,
Nov 15, 2019, 10:31:31 PM11/15/19
to Rayan Kanso, blink-dev
On Fri, Nov 15, 2019 at 11:25 AM Rayan Kanso <raya...@chromium.org> wrote:

Contact emails

fin...@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

Extends the Contacts API to allow developers to request contact addresses and icons as well.


Link to “Intent to Prototype” blink-dev discussion

https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/GBgoS_eCmzM/


Goals for experimentation

Is the address/icon information made available through the API sufficient to satisfy developer use-cases?

Specifically when sharing addresses, all available address information is stored in the addressLine attribute, but the broken down address attributes (postalCode, city, country, etc) are sometimes not available and left empty.


Experimental timeline

M80-M82


Any risks when the experiment finishes?

No, the shared information is one-off, users can choose not to share the information while it’s enabled, and there is an API for checking the supported contact properties.


Have this gone through security and privacy review?
 

Ongoing technical constraints

None


Will this feature be supported on all five Blink platforms supported by Origin Trials (Windows, Mac, Linux, Chrome OS, and Android)?

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.


Link to entry on the feature dashboard

https://www.chromestatus.com/feature/6511327140904960


--
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/CAAe2mZ0G21j5XcCK6C4r12EE0Mj0PVJgHz-zq%3D-MJ%3DsQZhgfmg%40mail.gmail.com.

Rayan Kanso

unread,
Nov 18, 2019, 9:03:09 AM11/18/19
to Yoav Weiss, blink-dev
It's going through privacy/security review. It's an extension to an API that's already been approved, so it would fall under the same constraints. I spoke to privacy/security reviewers in person, and they did not have any concerns, so I don't anticipate any issues resulting from the review.

Joe Medley

unread,
Nov 18, 2019, 12:55:53 PM11/18/19
to Rayan Kanso, blink-dev
Can you please create a new status entry.

Thank you,
Joe
Joe Medley | Technical Writer, Chrome DevRel | jme...@google.com | 816-678-7195
If an API's not documented it doesn't exist.


On Fri, Nov 15, 2019 at 11:25 AM Rayan Kanso <raya...@chromium.org> wrote:

Rayan Kanso

unread,
Nov 19, 2019, 12:07:23 PM11/19/19
to Joe Medley, Rayan Kanso, blink-dev

Chris Harrelson

unread,
Nov 21, 2019, 3:22:36 PM11/21/19
to Rayan Kanso, Joe Medley, Rayan Kanso, blink-dev
Reply all
Reply to author
Forward
0 new messages