public-webpayments-specs@w3.org from October 2017 by author

Adrian Hope-Bailie

• Re: [w3c/payment-request] Dealing with name as returned by the API (i18n) (#634) (Tuesday, 3 October)

Andrzej Rosiek

• Re: [w3c/payment-request] payment modifier brings error (#637) (Wednesday, 4 October)
• Re: [w3c/payment-request] payment modifier brings error (#637) (Wednesday, 4 October)
• Re: [w3c/payment-request] payment modifier brings error (#637) (Wednesday, 4 October)
• Re: [w3c/payment-request] payment modifier brings error (#637) (Wednesday, 4 October)
• Re: [w3c/payment-request] payment modifier brings error (#637) (Wednesday, 4 October)
• [w3c/payment-request] payment modifier brings error (#637) (Wednesday, 4 October)

Bill Hannah

• Re: [w3c/payment-request] Allow default option for donation in PaymentShippingType (#638) (Thursday, 5 October)
• Re: [w3c/payment-request] Allow default option for donation in PaymentShippingType (#638) (Thursday, 5 October)
• Re: [w3c/payment-request] Allow default option for donation in PaymentShippingType (#638) (Thursday, 5 October)
• [w3c/payment-request] Allow default option for donation in PaymentShippingType (#638) (Thursday, 5 October)

chinnagogulapati

• Re: [w3c/payment-request] Dealing with name as returned by the API (i18n) (#634) (Monday, 2 October)

Dominique Hazael-Massieux

• Re: [w3c/payment-request] Is browser support for PR API configurable? (#642) (Monday, 30 October)

dsajmr-commercial

• Re: [w3c/payment-request] Show example of .complete("unknown") (#584) (Sunday, 1 October)

ianbjacobs

• Re: [w3c/payment-handler] Allow Payment instrument to respond with user data (#218) (Thursday, 26 October)
• Re: [w3c/payment-request] Is browser support for PR API configurable? (#642) (Friday, 20 October)
• [w3c/payment-request] Is browser support for PR API configurable? (#642) (Friday, 20 October)
• Re: [w3c/payment-request] Should API support billing address capture (for tax computation)? (#27) (Tuesday, 17 October)
• Re: [w3c/payment-handler] "PaymentRequestEvent dictionary" makes no sense (#191) (Thursday, 12 October)
• Re: [w3c/payment-handler] "PaymentRequestEvent dictionary" makes no sense (#191) (Thursday, 12 October)
• Re: [w3c/payment-handler] respondWith behavior not specified (#190) (Thursday, 12 October)
• Re: [w3c/payment-handler] respondWith behavior not specified (#190) (Thursday, 12 October)
• Re: [w3c/payment-handler] Add explicit permission call to allow payment app to handle payments (#94) (Thursday, 12 October)
• Re: [w3c/payment-handler] Add explicit permission call to allow payment app to handle payments (#94) (Thursday, 12 October)
• Re: [w3c/payment-handler] Allow Payment instrument to respond with user data (#218) (Wednesday, 11 October)
• Re: [w3c/payment-handler] Add CanMakePaymentEvent. (#170) (Monday, 9 October)
• Re: [w3c/payment-request] Extract actionable items from @lknik's review (#641) (Monday, 9 October)
• Re: [w3c/payment-handler] Fixed small things in the text and code example (#220) (Monday, 9 October)
• Re: [w3c/payment-request] Third-party payment handlers (#640) (Sunday, 8 October)
• Re: [w3c/payment-request] Add way to update `total` and `displayItems` before `.show()` (#639) (Friday, 6 October)
• Re: [w3c/payment-handler] Clarification about data in PaymentRequestEvent (#219) (Wednesday, 4 October)
• Re: [w3c/payment-handler] Clarification about data in PaymentRequestEvent (#219) (Wednesday, 4 October)
• [w3c/payment-handler] Clarification about data in PaymentRequestEvent (#219) (Wednesday, 4 October)
• Re: [w3c/payment-handler] Return origin of payment app in PaymentHandlerResponse data? (#217) (Wednesday, 4 October)
• Re: [w3c/payment-handler] Return origin of payment app in PaymentHandlerResponse data? (#217) (Wednesday, 4 October)
• Re: [w3c/payment-handler] Return origin of payment app in PaymentHandlerResponse data? (#217) (Tuesday, 3 October)
• Re: [w3c/payment-handler] Return origin of payment app in PaymentHandlerResponse data? (#217) (Tuesday, 3 October)
• Re: [w3c/payment-handler] Return origin of payment app in PaymentHandlerResponse data? (#217) (Tuesday, 3 October)
• [w3c/payment-request] Editorial: Reuse "digital goods" (#636) (Tuesday, 3 October)
• Re: [w3c/payment-request] Dealing with name as returned by the API (i18n) (#634) (Monday, 2 October)
• Re: [w3c/payment-request] Handling Digital Assets (i.e. Bitcoin and Ethereum) (#635) (Monday, 2 October)
• Re: [w3c/payment-request] Handling Digital Assets (i.e. Bitcoin and Ethereum) (#635) (Monday, 2 October)

Jenan Wise

• Re: [w3c/payment-handler] Add CanMakePaymentEvent. (#170) (Sunday, 15 October)
• Re: [w3c/payment-handler] Add CanMakePaymentEvent. (#170) (Tuesday, 10 October)
• Re: [w3c/payment-request] Add way to update `total` and `displayItems` before `.show()` (#639) (Monday, 9 October)
• Re: [w3c/payment-request] Add way to update `total` and `displayItems` before `.show()` (#639) (Friday, 6 October)
• [w3c/payment-request] Add way to update `total` and `displayItems` before `.show()` (#639) (Friday, 6 October)

Jinho Bang

• Re: [w3c/payment-handler] Fixed small things in the text and code example (#220) (Tuesday, 10 October)

KOLANICH

• Re: [w3c/payment-request] Third-party payment handlers (#640) (Sunday, 8 October)
• [w3c/payment-request] Third-party payment handlers (#640) (Sunday, 8 October)

Krystian Czesak

• Re: [w3c/payment-handler] Allow Payment instrument to respond with user data (#218) (Thursday, 26 October)
• Re: [w3c/payment-handler] Allow Payment instrument to respond with user data (#218) (Wednesday, 11 October)

Lukasz Olejnik

• Re: [w3c/payment-request] Regulatory Compliance Support (#632) (Thursday, 12 October)
• Re: [w3c/payment-request] Extract actionable items from @lknik's review (#641) (Wednesday, 11 October)
• Re: [w3c/payment-request] Regulatory Compliance Support (#632) (Wednesday, 11 October)
• Re: [w3c/payment-request] Regulatory Compliance Support (#632) (Wednesday, 11 October)
• Re: [w3c/payment-request] Regulatory Compliance Support (#632) (Saturday, 7 October)

Marcos Cáceres

• Re: [w3c/payment-request] Is browser support for PR API configurable? (#642) (Monday, 30 October)
• Re: [w3c/payment-request] Is browser support for PR API configurable? (#642) (Saturday, 21 October)
• [w3c/payment-request] Extract actionable items from @lknik's review (#641) (Monday, 9 October)
• Re: [w3c/payment-request] Unclear what happens when multiple PRs call show() (#462) (Monday, 9 October)
• Re: [w3c/payment-request] Decide on currencySystem (#617) (Monday, 9 October)
• Re: [w3c/payment-request] Unclear what happens when multiple PRs call show() (#462) (Friday, 6 October)
• Re: [w3c/payment-request] Dealing with name as returned by the API (i18n) (#634) (Wednesday, 4 October)
• Re: [w3c/payment-request] Editorial: Reuse "digital goods" (#636) (Wednesday, 4 October)
• Re: [w3c/payment-handler] Return origin of payment app in PaymentHandlerResponse data? (#217) (Wednesday, 4 October)
• Re: [w3c/payment-handler] Return origin of payment app in PaymentHandlerResponse data? (#217) (Wednesday, 4 October)
• Re: [w3c/payment-handler] Return origin of payment app in PaymentHandlerResponse data? (#217) (Wednesday, 4 October)
• Re: [w3c/payment-handler] Return origin of payment app in PaymentHandlerResponse data? (#217) (Tuesday, 3 October)
• Re: [w3c/payment-handler] Return origin of payment app in PaymentHandlerResponse data? (#217) (Tuesday, 3 October)
• Re: [w3c/payment-handler] Return origin of payment app in PaymentHandlerResponse data? (#217) (Tuesday, 3 October)
• Re: [w3c/payment-request] Editorial: Reuse "digital goods" (#636) (Tuesday, 3 October)
• Re: [w3c/payment-request] Dealing with name as returned by the API (i18n) (#634) (Monday, 2 October)
• Re: [w3c/payment-request] onpaymentchange event to validate payment details (#634) (Monday, 2 October)

Mark Richards

• Re: [w3c/payment-request] Regulatory Compliance Support (#632) (Thursday, 12 October)
• Re: [w3c/payment-request] Regulatory Compliance Support (#632) (Thursday, 12 October)
• Re: [w3c/payment-request] Regulatory Compliance Support (#632) (Wednesday, 11 October)
• Re: [w3c/payment-request] Regulatory Compliance Support (#632) (Sunday, 8 October)

Matt N.

• Re: [w3c/payment-request] Is browser support for PR API configurable? (#642) (Monday, 30 October)

Michael[tm] Smith

• Re: [w3c/payment-request] Dealing with name as returned by the API (i18n) (#634) (Monday, 2 October)

michelle

• Re: [w3c/payment-request] Should API support billing address capture (for tax computation)? (#27) (Monday, 16 October)

Michelle, from Stripe

• Re: [w3c/payment-request] Should API support billing address capture (for tax computation)? (#27) (Monday, 16 October)

paranoid-android

• [w3c/payment-request] Handling Digital Assets (i.e. Bitcoin and Ethereum) (#635) (Monday, 2 October)

r12a

• Re: [w3c/payment-request] Dealing with name as returned by the API (i18n) (#634) (Monday, 2 October)

Rouslan Solomakhin

• Re: [w3c/payment-request] Is browser support for PR API configurable? (#642) (Friday, 20 October)
• Re: [w3c/payment-handler] Add CanMakePaymentEvent. (#170) (Tuesday, 10 October)
• Re: [w3c/payment-handler] Add CanMakePaymentEvent. (#170) (Monday, 9 October)
• Re: [w3c/payment-request] Add way to update `total` and `displayItems` before `.show()` (#639) (Friday, 6 October)
• Re: [w3c/payment-request] Add way to update `total` and `displayItems` before `.show()` (#639) (Friday, 6 October)
• Re: [w3c/payment-request] Allow default option for donation in PaymentShippingType (#638) (Thursday, 5 October)
• Re: [w3c/payment-request] Allow default option for donation in PaymentShippingType (#638) (Thursday, 5 October)
• Re: [w3c/payment-handler] Clarification about data in PaymentRequestEvent (#219) (Wednesday, 4 October)
• Re: [w3c/payment-handler] Clarification about data in PaymentRequestEvent (#219) (Wednesday, 4 October)
• Re: [w3c/payment-request] payment modifier brings error (#637) (Wednesday, 4 October)
• Re: [w3c/payment-request] payment modifier brings error (#637) (Wednesday, 4 October)
• Re: [w3c/payment-handler] Return origin of payment app in PaymentHandlerResponse data? (#217) (Wednesday, 4 October)
• Re: [w3c/payment-request] Dealing with name as returned by the API (i18n) (#634) (Tuesday, 3 October)

Wonsuk Lee

• [w3c/payment-handler] Fixed small things in the text and code example (#220) (Monday, 9 October)

Last message date: Monday, 30 October 2017 22:55:44 UTC