public-webpayments-specs@w3.org from December 2018 by thread

Re: [w3c/payment-request] consider requiring an error (non-empty dict) for .retry()? (#792) Matt N. (Wednesday, 19 December)

Re: [w3c/payment-handler] Drop PaymentInstrument in favor of MethodCapability (#302) ianbjacobs (Friday, 14 December)

[w3c/payment-request] Clarification question for `show()` algorithm (#820) Rouslan Solomakhin (Thursday, 13 December)

[w3c/payment-handler] chore: move former editors to the right place (#328) Marcos Cáceres (Wednesday, 12 December)

Re: [w3c/payment-handler] HTTPS considerations. (#283) Marcos Cáceres (Wednesday, 12 December)

[w3c/payment-request] Support for language the form is served (#819) Kennan Seno (Monday, 10 December)

[w3c/payment-request] Fix: WebIDL link for converting an ECMAScript value to a dictionary (#818) Wonsuk Lee (Friday, 7 December)

[w3c/payment-request] Extensibility of PaymentResponse.complete(result) (#817) Adrian Hope-Bailie (Thursday, 6 December)

Re: [w3c/payment-request] Clarify the behavior of calling PaymentResponse.complete() while [[retryPromise]] is pending (#795) Marcos Cáceres (Monday, 3 December)

Re: [w3c/payment-request] fix: while retrying complete() returns a rejected promise (#808) aestes (Monday, 3 December)

Re: [w3c/payment-request] Warn when errorFields don't match request[[options]] (#807) Marcos Cáceres (Sunday, 2 December)

Re: [w3c/payment-request] Should we validate nonsense payer error properties? (#793) Marcos Cáceres (Sunday, 2 December)

Last message date: Wednesday, 19 December 2018 19:19:57 UTC