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

Monday, 30 October 2017

Re: [w3c/payment-request] Is browser support for PR API configurable? (#642) Matt N.
Re: [w3c/payment-request] Is browser support for PR API configurable? (#642) Marcos Cáceres
Re: [w3c/payment-request] Is browser support for PR API configurable? (#642) Dominique Hazael-Massieux

Thursday, 26 October 2017

Re: [w3c/payment-handler] Allow Payment instrument to respond with user data (#218) ianbjacobs
Re: [w3c/payment-handler] Allow Payment instrument to respond with user data (#218) Krystian Czesak

Saturday, 21 October 2017

Re: [w3c/payment-request] Is browser support for PR API configurable? (#642) Marcos Cáceres

Friday, 20 October 2017

Re: [w3c/payment-request] Is browser support for PR API configurable? (#642) ianbjacobs
Re: [w3c/payment-request] Is browser support for PR API configurable? (#642) Rouslan Solomakhin
[w3c/payment-request] Is browser support for PR API configurable? (#642) ianbjacobs

Tuesday, 17 October 2017

Re: [w3c/payment-request] Should API support billing address capture (for tax computation)? (#27) ianbjacobs

Monday, 16 October 2017

Sunday, 15 October 2017

Re: [w3c/payment-handler] Add CanMakePaymentEvent. (#170) Jenan Wise

Thursday, 12 October 2017

Re: [w3c/payment-request] Regulatory Compliance Support (#632) Mark Richards
Re: [w3c/payment-request] Regulatory Compliance Support (#632) Lukasz Olejnik
Re: [w3c/payment-handler] "PaymentRequestEvent dictionary" makes no sense (#191) ianbjacobs
Re: [w3c/payment-handler] "PaymentRequestEvent dictionary" makes no sense (#191) ianbjacobs
Re: [w3c/payment-handler] respondWith behavior not specified (#190) ianbjacobs
Re: [w3c/payment-handler] respondWith behavior not specified (#190) ianbjacobs
Re: [w3c/payment-handler] Add explicit permission call to allow payment app to handle payments (#94) ianbjacobs
Re: [w3c/payment-handler] Add explicit permission call to allow payment app to handle payments (#94) ianbjacobs
Re: [w3c/payment-request] Regulatory Compliance Support (#632) Mark Richards

Wednesday, 11 October 2017

Re: [w3c/payment-handler] Allow Payment instrument to respond with user data (#218) ianbjacobs
Re: [w3c/payment-request] Extract actionable items from @lknik's review (#641) Lukasz Olejnik
Re: [w3c/payment-request] Regulatory Compliance Support (#632) Lukasz Olejnik
Re: [w3c/payment-handler] Allow Payment instrument to respond with user data (#218) Krystian Czesak
Re: [w3c/payment-request] Regulatory Compliance Support (#632) Mark Richards
Re: [w3c/payment-request] Regulatory Compliance Support (#632) Lukasz Olejnik

Tuesday, 10 October 2017

Re: [w3c/payment-handler] Add CanMakePaymentEvent. (#170) Rouslan Solomakhin
Re: [w3c/payment-handler] Fixed small things in the text and code example (#220) Jinho Bang
Re: [w3c/payment-handler] Add CanMakePaymentEvent. (#170) Jenan Wise

Monday, 9 October 2017

Re: [w3c/payment-handler] Add CanMakePaymentEvent. (#170) ianbjacobs
Re: [w3c/payment-handler] Add CanMakePaymentEvent. (#170) Rouslan Solomakhin
Re: [w3c/payment-request] Add way to update `total` and `displayItems` before `.show()` (#639) Jenan Wise
Re: [w3c/payment-request] Extract actionable items from @lknik's review (#641) ianbjacobs
Re: [w3c/payment-handler] Fixed small things in the text and code example (#220) ianbjacobs
[w3c/payment-handler] Fixed small things in the text and code example (#220) Wonsuk Lee
[w3c/payment-request] Extract actionable items from @lknik's review (#641) Marcos Cáceres
Re: [w3c/payment-request] Unclear what happens when multiple PRs call show() (#462) Marcos Cáceres
Re: [w3c/payment-request] Decide on currencySystem (#617) Marcos Cáceres

Sunday, 8 October 2017

Re: [w3c/payment-request] Third-party payment handlers (#640) KOLANICH
Re: [w3c/payment-request] Regulatory Compliance Support (#632) Mark Richards
Re: [w3c/payment-request] Third-party payment handlers (#640) ianbjacobs
[w3c/payment-request] Third-party payment handlers (#640) KOLANICH

Saturday, 7 October 2017

Re: [w3c/payment-request] Regulatory Compliance Support (#632) Lukasz Olejnik

Friday, 6 October 2017

Re: [w3c/payment-request] Add way to update `total` and `displayItems` before `.show()` (#639) ianbjacobs
Re: [w3c/payment-request] Add way to update `total` and `displayItems` before `.show()` (#639) Rouslan Solomakhin
Re: [w3c/payment-request] Add way to update `total` and `displayItems` before `.show()` (#639) Jenan Wise
Re: [w3c/payment-request] Add way to update `total` and `displayItems` before `.show()` (#639) Rouslan Solomakhin
Re: [w3c/payment-request] Unclear what happens when multiple PRs call show() (#462) Marcos Cáceres
[w3c/payment-request] Add way to update `total` and `displayItems` before `.show()` (#639) Jenan Wise

Thursday, 5 October 2017

Re: [w3c/payment-request] Allow default option for donation in PaymentShippingType (#638) Rouslan Solomakhin
Re: [w3c/payment-request] Allow default option for donation in PaymentShippingType (#638) Bill Hannah
Re: [w3c/payment-request] Allow default option for donation in PaymentShippingType (#638) Bill Hannah
Re: [w3c/payment-request] Allow default option for donation in PaymentShippingType (#638) Bill Hannah
Re: [w3c/payment-request] Allow default option for donation in PaymentShippingType (#638) Rouslan Solomakhin
[w3c/payment-request] Allow default option for donation in PaymentShippingType (#638) Bill Hannah

Wednesday, 4 October 2017

Re: [w3c/payment-handler] Clarification about data in PaymentRequestEvent (#219) ianbjacobs
Re: [w3c/payment-handler] Clarification about data in PaymentRequestEvent (#219) Rouslan Solomakhin
Re: [w3c/payment-handler] Clarification about data in PaymentRequestEvent (#219) ianbjacobs
Re: [w3c/payment-handler] Clarification about data in PaymentRequestEvent (#219) Rouslan Solomakhin
[w3c/payment-handler] Clarification about data in PaymentRequestEvent (#219) ianbjacobs
Re: [w3c/payment-request] payment modifier brings error (#637) Andrzej Rosiek
Re: [w3c/payment-request] payment modifier brings error (#637) Andrzej Rosiek
Re: [w3c/payment-request] payment modifier brings error (#637) Rouslan Solomakhin
Re: [w3c/payment-request] payment modifier brings error (#637) Andrzej Rosiek
Re: [w3c/payment-request] payment modifier brings error (#637) Rouslan Solomakhin
Re: [w3c/payment-request] payment modifier brings error (#637) Andrzej Rosiek
Re: [w3c/payment-request] payment modifier brings error (#637) Andrzej Rosiek
[w3c/payment-request] payment modifier brings error (#637) Andrzej Rosiek
Re: [w3c/payment-handler] Return origin of payment app in PaymentHandlerResponse data? (#217) Rouslan Solomakhin
Re: [w3c/payment-request] Dealing with name as returned by the API (i18n) (#634) Marcos Cáceres
Re: [w3c/payment-request] Editorial: Reuse "digital goods" (#636) Marcos Cáceres
Re: [w3c/payment-handler] Return origin of payment app in PaymentHandlerResponse data? (#217) Marcos Cáceres
Re: [w3c/payment-handler] Return origin of payment app in PaymentHandlerResponse data? (#217) Marcos Cáceres
Re: [w3c/payment-handler] Return origin of payment app in PaymentHandlerResponse data? (#217) ianbjacobs
Re: [w3c/payment-handler] Return origin of payment app in PaymentHandlerResponse data? (#217) Marcos Cáceres
Re: [w3c/payment-handler] Return origin of payment app in PaymentHandlerResponse data? (#217) ianbjacobs

Tuesday, 3 October 2017

Re: [w3c/payment-handler] Return origin of payment app in PaymentHandlerResponse data? (#217) Marcos Cáceres
Re: [w3c/payment-handler] Return origin of payment app in PaymentHandlerResponse data? (#217) ianbjacobs
Re: [w3c/payment-handler] Return origin of payment app in PaymentHandlerResponse data? (#217) Marcos Cáceres
Re: [w3c/payment-handler] Return origin of payment app in PaymentHandlerResponse data? (#217) ianbjacobs
Re: [w3c/payment-handler] Return origin of payment app in PaymentHandlerResponse data? (#217) Marcos Cáceres
Re: [w3c/payment-handler] Return origin of payment app in PaymentHandlerResponse data? (#217) ianbjacobs
Re: [w3c/payment-request] Editorial: Reuse "digital goods" (#636) Marcos Cáceres
[w3c/payment-request] Editorial: Reuse "digital goods" (#636) ianbjacobs
Re: [w3c/payment-request] Dealing with name as returned by the API (i18n) (#634) Rouslan Solomakhin
Re: [w3c/payment-request] Dealing with name as returned by the API (i18n) (#634) Adrian Hope-Bailie

Monday, 2 October 2017

Re: [w3c/payment-request] Dealing with name as returned by the API (i18n) (#634) ianbjacobs
Re: [w3c/payment-request] Dealing with name as returned by the API (i18n) (#634) chinnagogulapati
Re: [w3c/payment-request] Handling Digital Assets (i.e. Bitcoin and Ethereum) (#635) ianbjacobs
Re: [w3c/payment-request] Handling Digital Assets (i.e. Bitcoin and Ethereum) (#635) ianbjacobs
[w3c/payment-request] Handling Digital Assets (i.e. Bitcoin and Ethereum) (#635) paranoid-android
Re: [w3c/payment-request] Dealing with name as returned by the API (i18n) (#634) r12a
Re: [w3c/payment-request] Dealing with name as returned by the API (i18n) (#634) Michael[tm] Smith
Re: [w3c/payment-request] Dealing with name as returned by the API (i18n) (#634) Marcos Cáceres
Re: [w3c/payment-request] onpaymentchange event to validate payment details (#634) Marcos Cáceres

Sunday, 1 October 2017

Re: [w3c/payment-request] Show example of .complete("unknown") (#584) dsajmr-commercial

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