public-webpayments-specs@w3.org from September 2018 by date

Sunday, 30 September 2018

Re: [w3c/payment-method-id] Generate an implementation report (#54) ianbjacobs
Re: [w3c/payment-request] Confirm tests and specs align (#779) ianbjacobs
Re: [w3c/payment-request] Confirm tests and specs align (#779) Sylvia Mittal
Re: [w3c/payment-request] Confirm tests and specs align (#779) Marcos Cáceres
[w3c/payment-method-id] Prepare for Proposed Recommendation (#56) Marcos Cáceres
Re: [w3c/payment-method-id] Generate an implementation report (#54) Marcos Cáceres
Re: [w3c/payment-method-id] Updated the link to the test-suit (#55) Marcos Cáceres
[w3c/payment-request] Issue #782 - Renames PayerErrorFields to PayerErrors (#789) Akansha
Re: [w3c/payment-method-id] Updated the link to the test-suit (#55) Yatri Patel
Re: [w3c/payment-method-id] Updated the link to the test-suit (#55) Yatri Patel

Saturday, 29 September 2018

Friday, 28 September 2018

Re: [w3c/payment-request] Fix #787 : Fix the links to the `data-tests` in the spec (#788) Sylvia Mittal
Re: [w3c/payment-request] Fix the links to the `data-tests` in the spec (#787) Marcos Cáceres
Re: [w3c/payment-request] Fix #787 : Fix the links to the `data-tests` in the spec (#788) Marcos Cáceres
Re: [w3c/payment-request] Fix #787 : Fix the links to the `data-tests` in the spec (#788) Marcos Cáceres
Re: [w3c/payment-request] Fix #787 : Fix the links to the `data-tests` in the spec (#788) Marcos Cáceres
Re: [w3c/payment-request] Confirm tests and specs align (#779) Sylvia Mittal
[w3c/payment-request] Fix #787 : Fix the links to the `data-tests` in the spec (#788) Sylvia Mittal
[w3c/payment-request] Fix the links to the `data-tests` in the spec (#787) Sylvia Mittal
Re: [w3c/payment-request] fix: give dictionary members sensible defaults (#781) Marcos Cáceres
Re: [w3c/payment-request] fix: give dictionary members sensible defaults (#781) Marcos Cáceres
Re: [w3c/payment-request] "data-test" should be changed to "data-tests" in spec (#785) Marcos Cáceres
Re: [w3c/payment-request] "data-test" should be changed to "data-tests" in spec (#785) Marcos Cáceres
Re: [w3c/payment-request] Fix #785 : data-test should be changed to data-tests in spec (#786) Marcos Cáceres
Re: [w3c/payment-request] Fix #785 : data-test should be changed to data-tests in spec (#786) Marcos Cáceres
Re: [w3c/payment-request] Fix #785 : data-test should be changed to data-tests in spec (#786) Marcos Cáceres
[w3c/payment-request] Fix #785 : data-test should be changed to data-tests in spec (#786) Sylvia Mittal
[w3c/payment-request] "data-test" should be changed to "data-tests" in spec (#785) Sylvia Mittal
Re: [w3c/payment-method-id] Updated the link to the test-suit (#55) Marcos Cáceres
Re: [w3c/payment-request] Fix #779 : Confirm test and specs align (#784) Marcos Cáceres
Re: [w3c/payment-request] Fix #779 : Confirm test and specs align (#784) Marcos Cáceres
Re: [w3c/payment-method-id] Updated the link to the test-suit (#55) Yatri Patel
Re: [w3c/payment-method-id] Updated the link to the test-suit (#55) Marcos Cáceres
Re: [w3c/payment-method-id] Generate an implementation report (#54) Yatri Patel

Thursday, 27 September 2018

[w3c/payment-request] Fix #779 : Confirm test and specs align (#784) Sylvia Mittal
Re: [w3c/payment-method-id] Updated the link to the test-suit (#55) Yatri Patel
Re: [w3c/payment-method-id] Updated the link to the test-suit (#55) Yatri Patel
Re: [w3c/payment-handler] [WIP] showPaymentUI() method (#325) Rouslan Solomakhin
Re: [w3c/payment-handler] [WIP] showPaymentUI() method (#325) Jinho Bang
Re: [w3c/payment-method-id] Updated the link to the test-suit (#55) Marcos Cáceres
Re: [w3c/payment-method-id] Updated the link to the test-suit (#55) Marcos Cáceres
Re: [w3c/payment-method-id] Updated the link to the test-suit (#55) Yatri Patel
Re: [w3c/payment-method-id] Updated the link to the test-suit (#55) Yatri Patel
Re: [w3c/payment-method-id] Updated the link to the test-suit (#55) Marcos Cáceres
Re: [w3c/payment-method-id] Updated the link to the test-suit (#55) Marcos Cáceres
Re: [w3c/payment-method-id] Generate an implementation report (#54) Marcos Cáceres
[w3c/payment-method-id] Updated the link to the test-suit (#55) Yatri Patel
Re: [w3c/payment-method-id] Generate an implementation report (#54) Yatri Patel
Re: [w3c/payment-request] Editorial: fix link to basic card error dictionary in examples (#783) Marcos Cáceres
Re: [w3c/payment-request] Fix link to basic card error dictionary in examples (#783) Marcos Cáceres
Re: [w3c/payment-request] Fix link to basic card error dictionary in examples (#783) Marcos Cáceres
[w3c/payment-request] Fix link to basic card error dictionary in examples (#783) Matt N.
Re: [w3c/payment-request] Rename `PayerErrorFields` to be like `AddressErrors` and `BasicCardErrors` (#782) Marcos Cáceres
[w3c/payment-request] Rename `PayerErrorFields` to be like `AddressErrors` and `BasicCardErrors` (#782) Matt N.

Wednesday, 26 September 2018

Re: [w3c/payment-method-id] Generate an implementation report (#54) Marcos Cáceres
Re: [w3c/payment-method-id] Generate an implementation report (#54) Marcos Cáceres
Re: [w3c/payment-method-id] Generate an implementation report (#54) Yatri Patel
Re: [w3c/payment-method-id] Generate an implementation report (#54) Marcos Cáceres
Re: [w3c/payment-method-id] Generate an implementation report (#54) Yatri Patel
Re: [w3c/payment-method-id] Generate an implementation report (#54) Marcos Cáceres
Re: [w3c/payment-method-id] Generate an implementation report (#54) Marcos Cáceres
Re: [w3c/payment-method-id] Generate an implementation report (#54) Yatri Patel
Re: [w3c/payment-method-id] Generate an implementation report (#54) Marcos Cáceres
Re: [w3c/payment-method-id] Generate an implementation report (#54) Yatri Patel
Re: [w3c/payment-method-id] Generate an implementation report (#54) Yatri Patel
Re: [w3c/payment-method-id] Generate an implementation report (#54) Marcos Cáceres
Re: [w3c/payment-method-id] Generate an implementation report (#54) Yatri Patel
Re: [w3c/payment-handler] Code of Conduct (#326) Philippe Le Hegaret
Re: [w3c/payment-method-id] Editorial: describe relationship to pay manifest (#53) Marcos Cáceres
Re: [w3c/payment-method-id] What can I do with a URL-based payment method identifier? (#52) Marcos Cáceres
Re: [w3c/payment-handler] Code of Conduct (#326) ianbjacobs
[w3c/payment-handler] Code of Conduct (#326) Philippe Le Hegaret
Re: [w3c/payment-method-id] Generate an implementation report (#54) ianbjacobs
Re: [w3c/payment-method-id] Editorial: describe relationship to pay manifest (#53) ianbjacobs
Re: [w3c/payment-method-id] Generate an implementation report (#54) Yatri Patel
[w3c/payment-request] fix: give dictionary member sensible defaults (#781) Marcos Cáceres
[w3c/payment-request] Sensible defaults for dictionary members (#780) Marcos Cáceres
Re: [w3c/payment-request] Confirm test and specs align (#779) Sylvia Mittal
[w3c/payment-request] Confirm test and specs align (#779) Marcos Cáceres
[w3c/payment-method-id] Generate an implementation report (#54) Marcos Cáceres
Re: [w3c/payment-method-id] Editorial: describe relationship to pay manifest (#53) Marcos Cáceres
[w3c/payment-method-id] Editorial: describe relationship to pay manifest (#53) Marcos Cáceres

Tuesday, 25 September 2018

Re: [w3c/payment-request] Add support for crypto currencies (#627) Giorgio Tedesco

Monday, 24 September 2018

Re: [w3c/payment-handler] [WIP] showPaymentUI() method (#325) Dave Longley
Re: [w3c/payment-handler] [WIP] showPaymentUI() method (#325) Rouslan Solomakhin
Re: [w3c/payment-handler] [WIP] showPaymentUI() method (#325) ianbjacobs
Re: [w3c/payment-handler] [WIP] showPaymentUI() method (#325) Rouslan Solomakhin
Re: [w3c/payment-handler] [WIP] showPaymentUI() method (#325) Jinho Bang
[w3c/payment-handler] [WIP] showPaymentUI() method (#325) Jinho Bang
Re: [w3c/webpayments-methods-tokenization] Add flow diagrams to the spec (#50) ianbjacobs

Friday, 21 September 2018

Thursday, 20 September 2018

Re: [w3c/payment-handler] Update Example6 and Example7 (#290) Jinho Bang
Re: [w3c/payment-handler] Suggest changing a shape of openWindow() (#300) Jinho Bang
Re: [w3c/payment-method-basic-card] Signaling payment handler details errors (#57) Marcos Cáceres
Re: [w3c/payment-method-basic-card] add BasicCardErrors (#58) Marcos Cáceres
Re: [w3c/payment-method-basic-card] User changes payment method (#53) Marcos Cáceres
Re: [w3c/payment-handler] Simplifying functional event handling (#305) Marcos Cáceres
Re: [w3c/payment-handler] Simplifying functional event handling (#305) Jake Archibald

Wednesday, 19 September 2018

Re: [w3c/payment-handler] Simplifying functional event handling (#305) Rouslan Solomakhin
Re: [w3c/payment-handler] Simplifying functional event handling (#305) Rouslan Solomakhin
Re: [w3c/payment-handler] Update Example6 and Example7 (#290) Rouslan Solomakhin
Re: [w3c/payment-handler] Remove link to issue 157 (#292) ianbjacobs
Re: [w3c/payment-handler] Remove link to issue 157 (#292) ianbjacobs
Re: [w3c/payment-handler] Cross-origin iframes and feature policy. (#282) Rouslan Solomakhin
Re: [w3c/payment-handler] Cross-origin iframes and feature policy. (#282) Rouslan Solomakhin
Re: [w3c/payment-handler] Remove requestPermission() (#277) Rouslan Solomakhin
Re: [w3c/payment-handler] Proposal: Remove requestPermission() (#246) Rouslan Solomakhin
Re: [w3c/payment-handler] Remove requestPermission() (#277) Rouslan Solomakhin
Re: [w3c/payment-handler] Remove requestPermission() (#277) ianbjacobs
Re: [w3c/payment-handler] Remove requestPermission() (#277) Rouslan Solomakhin
Re: [w3c/payment-handler] Only allows instrument.set() in active service worker (#224) Rouslan Solomakhin
Re: [w3c/payment-handler] How would iDeal work? (#251) ianbjacobs
Re: [w3c/payment-handler] How would iDeal work? (#251) Bart
Re: [w3c/payment-handler] Support for Abort() being delegated to Payment Handler (#117) ianbjacobs
Re: [w3c/payment-handler] Add AbortPaymentEvent. (#207) Rouslan Solomakhin
Re: [w3c/payment-handler] Add AbortPaymentEvent. (#207) Rouslan Solomakhin
Re: [w3c/payment-handler] (Editorial) Clarify validation expectation (#324) Rouslan Solomakhin
Re: [w3c/payment-handler] What should payees validate? (#310) Rouslan Solomakhin
Re: [w3c/payment-handler] (Editorial) Clarify validation expectation (#324) Rouslan Solomakhin
Re: [w3c/payment-handler] (Editorial) Clarify validation expectation (#324) ianbjacobs
[w3c/payment-handler] (Editorial) Clarify validation expectation (#324) ianbjacobs
Re: [w3c/payment-handler] (Editorial) fix storedInstrument per issue 316 (#323) Rouslan Solomakhin
Re: [w3c/payment-handler] Examples involving storedInstrument seem broken (#316) Rouslan Solomakhin
Re: [w3c/payment-handler] (Editorial) fix storedInstrument per issue 316 (#323) Rouslan Solomakhin
[w3c/payment-handler] (Editorial) fix storedInstrument per issue 316 (#323) ianbjacobs
Re: [w3c/payment-handler] Open Window Algorithm (#115) ianbjacobs
Re: [w3c/payment-handler] Open Window Algorithm (#115) ianbjacobs
Re: [w3c/payment-handler] How would iDeal work? (#251) ianbjacobs
Re: [w3c/payment-handler] How would iDeal work? (#251) ianbjacobs
Re: [w3c/payment-handler] Links to terms and common terminology (#50) ianbjacobs
Re: [w3c/payment-handler] Links to terms and common terminology (#50) ianbjacobs
Re: [w3c/payment-handler] Link for "fetching image object" is broken (#317) Rouslan Solomakhin
Re: [w3c/payment-handler] (Editorial) link fix for issue 317 (#322) Rouslan Solomakhin
Re: [w3c/payment-handler] (Editorial) link fix for issue 317 (#322) Rouslan Solomakhin
[w3c/payment-handler] (Editorial) link fix for issue 317 (#322) ianbjacobs
Re: [w3c/payment-handler] Payment Handler window `.focused` field (#307) ianbjacobs
Re: [w3c/payment-handler] Payment Handler window `.focused` field (#307) ianbjacobs
[w3c/payment-handler] Update Open Window Algorithm (#321) ianbjacobs
Re: [w3c/payment-handler] Payment Handler window `.focused` field (#307) Rouslan Solomakhin
Re: [w3c/payment-handler] Added more security implementation notes from Rouslan; non-normative (#320) Rouslan Solomakhin
Re: [w3c/payment-handler] Added more security implementation notes from Rouslan; non-normative (#320) Rouslan Solomakhin
[w3c/payment-handler] Added more security implementation notes from Rouslan; non-normative (#320) ianbjacobs
Re: [w3c/payment-handler] Suggest changing a shape of openWindow() (#300) Rouslan Solomakhin
Re: [w3c/payment-handler] What mechanism allows enforcing payment handler authenticity? (#308) ianbjacobs
Re: [w3c/payment-handler] What mechanism allows enforcing payment handler authenticity? (#308) ianbjacobs
Re: [w3c/payment-request] Add paymentMethodErrors, payerErrors, to PaymentDetailsUpdate (#768) Marcos Cáceres
Re: [w3c/payment-request] PaymentDetailsUpdate needs to include payerErrors (#766) Marcos Cáceres
Re: [w3c/payment-request] Add paymentMethodErrors, payerErrors, to PaymentDetailsUpdate (#768) Marcos Cáceres

Tuesday, 18 September 2018

Re: [w3c/payment-request] Not able to add shipping options dynamically for apple pay (#778) Siddeshwaraswamy
Re: [w3c/payment-request] Not able to add shipping options dynamically for apple pay (#778) Marcos Cáceres
Re: [w3c/payment-request] Not able to add shipping options dynamically for apple pay (#778) Marcos Cáceres
Re: [w3c/payment-request] Not able to add shipping options dynamically for apple pay (#778) Siddeshwaraswamy
Re: [w3c/payment-handler] Notify merchant that payment method (possibly including the billing address) changed in payment handler. (#318) Philip Jägenstedt
Re: [w3c/payment-request] Not able to add shipping options dynamically for apple pay (#778) Marcos Cáceres
Re: [w3c/payment-request] Not able to add shipping options dynamically for apple pay (#778) Siddeshwaraswamy
Re: [w3c/payment-request] Not able to add shipping options dynamically for apple pay (#778) Marcos Cáceres
[w3c/payment-request] Not able to add shipping options for apple pay (#778) Siddeshwaraswamy

Monday, 17 September 2018

Saturday, 15 September 2018

Re: [w3c/payment-handler] Fix Web IDL typo: bool → boolean (#319) Marcos Cáceres
Re: [w3c/payment-handler] Fix Web IDL typo: bool → boolean (#319) Marcos Cáceres
[w3c/payment-handler] Fix Web IDL typo: bool → boolean (#319) Philip Jägenstedt
Re: [w3c/payment-handler] Notify merchant that payment method (possibly including the billing address) changed in payment handler. (#318) Philip Jägenstedt
Re: [w3c/payment-handler] Notify merchant that payment method (possibly including the billing address) changed in payment handler. (#318) Philip Jägenstedt
Re: [w3c/payment-request] Add paymentMethodErrors, payerErrors, to PaymentDetailsUpdate (#768) Jinho Bang

Friday, 14 September 2018

Re: [w3c/payment-request] Integration with Feature Policy (#600) Ian Clelland
Re: [w3c/payment-request] Integration with Feature Policy (#600) Ian Clelland
Re: [w3c/payment-request] Integration with Feature Policy (#600) Luna Lu
Re: [w3c/payment-request] Integration with Feature Policy (#600) Rouslan Solomakhin
Re: [w3c/payment-request] Integration with Feature Policy (#600) Rouslan Solomakhin
Re: [w3c/payment-handler] Add support for communicating billing address to merchant (e.g., for VAT computation) (#314) Rouslan Solomakhin
Re: [w3c/payment-handler] Notify merchant that payment method (possibly including the billing address) changed in payment handler. (#318) Rouslan Solomakhin
Re: [w3c/payment-handler] Suggest changing a shape of openWindow() (#300) Rouslan Solomakhin
Re: [w3c/payment-handler] Suggest changing a shape of openWindow() (#300) Jinho Bang
Re: [w3c/payment-handler] Notify merchant that payment method (possibly including the billing address) changed in payment handler. (#318) Jinho Bang
Re: [w3c/payment-request] Integration with Feature Policy (#600) Marcos Cáceres
Re: [w3c/payment-request] Integration with Feature Policy (#600) Marcos Cáceres

Thursday, 13 September 2018

Re: [w3c/payment-request] To address branded button issues and improve privacy, add browser support for payment method selection before the sheet (#777) Dave Longley
Re: [w3c/payment-handler] Notify merchant that payment method (possibly including the billing address) changed in payment handler. (#318) Rouslan Solomakhin
Re: [w3c/payment-handler] Notify merchant that payment method (possibly including the billing address) changed in payment handler. (#318) Rouslan Solomakhin
Re: [w3c/payment-handler] Suggest changing a shape of openWindow() (#300) Rouslan Solomakhin
Re: [w3c/payment-request] Some clarifications with Payment Request API (#774) ianbjacobs
Re: [w3c/payment-request] Add paymentMethodErrors, payerErrors, to PaymentDetailsUpdate (#768) Marcos Cáceres
Re: [w3c/payment-handler] Suggest changing a shape of openWindow() (#300) Jinho Bang
Re: [w3c/payment-handler] Notify merchant that payment method (possibly including the billing address) changed in payment handler. (#318) Jinho Bang
Re: [w3c/payment-request] Add paymentMethodErrors, payerErrors, to PaymentDetailsUpdate (#768) Jinho Bang
Re: [w3c/payment-request] Add paymentMethodErrors, payerErrors, to PaymentDetailsUpdate (#768) Marcos Cáceres
Re: [w3c/payment-request] Add paymentMethodErrors, payerErrors, to PaymentDetailsUpdate (#768) Marcos Cáceres
Re: [w3c/payment-request] Some clarifications with Payment Request API (#774) Marcos Cáceres
Re: [w3c/payment-request] Some clarifications with Payment Request API (#774) Marcos Cáceres
Re: [w3c/payment-request] Some clarifications with Payment Request API (#774) Marcos Cáceres
Re: [w3c/payment-request] Add MerchantValidationEvent.prototype.methodName (#776) Marcos Cáceres
Re: [w3c/payment-request] Do we need to identify payment method in MerchantValidationEvent? (#775) Marcos Cáceres
Re: [w3c/payment-request] Add MerchantValidationEvent.prototype.methodName (#776) Marcos Cáceres
Re: [w3c/payment-request] Add MerchantValidationEvent.prototype.methodName (#776) Marcos Cáceres
Re: [w3c/payment-request] Add MerchantValidationEvent.prototype.methodName (#776) Jinho Bang
Re: [w3c/payment-request] Some clarifications with Payment Request API (#774) Eiji Kitamura
Re: [w3c/payment-request] Add MerchantValidationEvent.prototype.methodName (#776) Marcos Cáceres
Re: [w3c/payment-request] Add MerchantValidationEvent.prototype.methodName (#776) Marcos Cáceres

Wednesday, 12 September 2018

Tuesday, 11 September 2018

Monday, 10 September 2018

Re: [w3c/webpayments-methods-tokenization] Distinguish full tokenized-card from token-reference (lighter payment method) (#46) ianbjacobs
Re: [w3c/webpayments-methods-tokenization] How are future card on file transactions supported through dynamic data? (#44) ianbjacobs
Re: [w3c/payment-method-basic-card] add BasicCardErrors (#58) Domenic Denicola
Re: [w3c/payment-request] Should API support billing address capture (for tax computation)? (#27) Christos Constantinou
Re: [w3c/payment-method-basic-card] add BasicCardErrors (#58) Marcos Cáceres

Saturday, 8 September 2018

Re: [w3c/payment-request] Make billing address optional (#773) Eiji Kitamura
Re: [w3c/payment-request] Remove PaymentAddress' languageCode (#765) Marcos Cáceres

Friday, 7 September 2018

Re: [w3c/payment-request] Make billing address optional (#773) Marcos Cáceres
Re: [w3c/payment-request] Make billing address optional (#773) Marcos Cáceres
Re: [w3c/payment-request] Make billing address optional (#773) Jinho Bang
[w3c/payment-request] Make billing address optional (#773) Eiji Kitamura
Re: [w3c/payment-handler] PaymentManager behavior unclear (#253) Rouslan Solomakhin
Re: [w3c/payment-handler] Simplifying functional event handling (#305) Rouslan Solomakhin
Re: [w3c/payment-handler] Simplifying functional event handling (#305) Rouslan Solomakhin
Re: [w3c/payment-handler] Simplifying functional event handling (#305) Rouslan Solomakhin
Re: [w3c/payment-handler] Simplifying functional event handling (#305) Rouslan Solomakhin
Re: [w3c/payment-handler] Simplifying functional event handling (#305) Rouslan Solomakhin
Re: [w3c/payment-request] Extract actionable items from Shopify study (#772) ianbjacobs
Re: [w3c/payment-handler] Simplifying functional event handling (#305) Jake Archibald
Re: [w3c/payment-handler] PaymentManager behavior unclear (#253) Jonas Mendes
[w3c/payment-request] Extract actionable items from Shopify study (#772) Marcos Cáceres

Thursday, 6 September 2018

Re: [w3c/payment-request] Describe how to implement PaymentAddress.languageCode (#608) Peter Saint-Andre
Re: [w3c/payment-handler] PaymentManager behavior unclear (#253) ianbjacobs
Re: [w3c/payment-handler] PaymentManager behavior unclear (#253) Rouslan Solomakhin
Re: [w3c/payment-handler] PaymentManager behavior unclear (#253) Rouslan Solomakhin
Re: [w3c/payment-handler] PaymentManager behavior unclear (#253) Jonas Mendes
Re: [w3c/payment-request] Remove PaymentAddress' languageCode (#765) Marcos Cáceres
Re: [w3c/payment-request] Remove PaymentAddress' languageCode (#765) ianbjacobs
Re: [w3c/payment-request] Remove PaymentAddress' languageCode (#765) Adrian Hope-Bailie
Re: [w3c/payment-request] editorial: mark languageCode at risk (#764) Marcos Cáceres

Wednesday, 5 September 2018

Re: [w3c/payment-request] editorial: mark languageCode at risk (#764) Peter Saint-Andre
Re: [w3c/payment-request] editorial: mark languageCode at risk (#764) Peter Saint-Andre
Re: [w3c/payment-request] editorial: mark languageCode at risk (#764) Marcos Cáceres
Re: [w3c/payment-request] editorial: mark languageCode at risk (#764) Addison Phillips
Re: [w3c/payment-request] editorial: mark languageCode at risk (#764) Marcos Cáceres
Re: [w3c/payment-request] editorial: mark languageCode at risk (#764) Peter Saint-Andre
Re: [w3c/payment-request] Add link to SecureContext test (#697) Marcos Cáceres
Re: [w3c/payment-request] Populate implementation report (#560) Marcos Cáceres
Re: [w3c/payment-request] Populate implementation report (#560) Marcos Cáceres

Tuesday, 4 September 2018

Re: [w3c/payment-request] Remove PaymentAddress' languageCode (#765) aestes
Re: [w3c/payment-request] fix: give PaymentMethodChangeEventInit defaults (#771) Marcos Cáceres
Re: [w3c/payment-request] Can PaymentMethodChangeEventInit really have a required member? (#770) Marcos Cáceres
Re: [w3c/payment-request] fix: give PaymentMethodChangeEventInit defaults (#771) Marcos Cáceres
Re: [w3c/payment-request] fix: give PaymentMethodChangeEventInit defaults (#771) Marcos Cáceres
Re: [w3c/payment-request] Add paymentMethodErrors, payerErrors, to PaymentDetailsUpdate (#768) Marcos Cáceres
Re: [w3c/payment-request] Remove PaymentAddress' languageCode (#765) Marcos Cáceres

Monday, 3 September 2018

Re: [w3c/payment-request] Add paymentMethodErrors, payerErrors, to PaymentDetailsUpdate (#768) Jinho Bang

Last message date: Sunday, 30 September 2018 15:05:25 UTC