[w3ctag/design-reviews] [Payments] shipping and contact info delegation (#425)

こんにちはTAG!

I'm requesting a TAG review of:

  - Name: Delegate handling of shipping address and payer's contact info to payment handlers.
  - Explainer: https://github.com/sahel-sh/shipping-contact-delegation/blob/master/Explainer.md

  - Tests: 
  [enable-shipping-contact-delegation](third_party/blink/web_tests/external/wpt/payment-handler/supports-shipping-contact-delegation-manual.https.html)
[change-shipping-option](third_party/blink/web_tests/external/wpt/payment-handler/change-shipping-option-manual.https.html)
[change-shipping-address](third_party/blink/web_tests/external/wpt/payment-handler/change-shipping-address-manual.https.html)

  - Primary contacts: @sahel-sh (editor)

Further details:

  - Relevant time constraints or deadlines: We would like to ship this in Chrome 80 (feature freeze deadline is Nov 15, 2019)
  - [x] I have read and filled out the [Self-Review Questionnare on Security and Privacy](https://www.w3.org/TR/security-privacy-questionnaire/). The [assessment is here](url).
  - [x] I have reviewed the TAG's [API Design Principles](https://w3ctag.github.io/design-principles/)
  - The group where the work on this specification is: Web Payment Working Group

You should also know that...

We have a working prototype implemented in Chromium behind web platform experimental features flags. A lot of merchants and payment apps showed interest in our demo at TPAC-2019, in addition to discussions here:
https://github.com/w3c/payment-handler/issues/337


We'd prefer the TAG provide feedback as (please select one):

  - [ ] open issues in our GitHub repo for each point of feedback
  - [ ] open a single issue in our GitHub repo for the entire review
  - [x] leave review feedback as a comment in this issue and @-notify @sahel-sh

--------------------------

_Please preview the issue and check that the links work before submitting._ In particular, if anything links to a URL which requires authentication (e.g. Google document), please make sure anyone with the link can access the document.

¹ For background, see our [explanation of how to write a good explainer](https://w3ctag.github.io/explainers).


-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/425