- From: Ian Jacobs <ij@w3.org>
- Date: Mon, 21 Aug 2017 15:34:53 -0500
- To: Payments WG <public-payments-wg@w3.org>
Participants in the payments app task force, We meet 22 August from 10-11am ET. WebEx: http://www.w3.org/2017/01/paymentapps-2017.ics Previous meeting: 25 July https://www.w3.org/2017/07/25-apps-minutes (We did not meet on 8 August) Proposed next meeting: 29 August Ian ========== Agenda * Add CanMakePaymentEvent and AbortPaymentEvent https://github.com/w3c/payment-handler/pull/170 We came close to merging this pull request to add two new event types to the specification. However, Adam Roach expressed privacy concerns. Let's discuss! Related issues: 157, 117 * Service workers example from Rouslan to illustrate how to publish two "wallets" from the origin. Should we add this example to the spec? Or to the developer portal? Are there issues with the example? https://github.com/rsolomakhin/rsolomakhin.github.io/blob/master/pr/sw.md I believe that once we've resolved what to do with the example, we can close issue 153. * Issue 178: Default handler icon. Can we make progress on this? See Rouslan's proposal: https://github.com/w3c/payment-handler/issues/178#issuecomment-309778321 and my follow-up: https://github.com/w3c/payment-handler/issues/178#issuecomment-309947884 * Issue 190: respondWith behavior not specified Issue 191: "PaymentRequestEvent dictionary" makes no sense This has a pull request that has had some review: https://github.com/w3c/payment-handler/pull/194 Are we ok to merge the pull request? Also, does that pull request also address issue 191? https://github.com/w3c/payment-handler/issues/191 * Pull request: Add "Validate Methods Algorithm" https://github.com/w3c/payment-handler/pull/197 This is an important security-related pull request. It also creates a new dependency on the payment method manifest specification. * Issue 116: Relation between merchant order of payment methods and payment app order of instruments. See Ian proposal for language (supported by Rouslan): https://github.com/w3c/payment-handler/issues/116#issuecomment-317890522 Another idea is to remove the requirement language entirely. * Issue 203: Make explicit which origin to use in conjunction with payment method manifest https://github.com/w3c/payment-handler/issues/203 * Issue 173: Marcos has sent comments indicating that this needs more work. Anyone want to develop the proposal? https://github.com/w3c/payment-handler/issues/173 * Next meeting: Proposed 29 August.
Received on Monday, 21 August 2017 20:34:55 UTC