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

Adam Solove

• Re: [w3c/payment-request] To address branded button issues and improve privacy, add browser support for payment method selection before the sheet (#777) (Wednesday, 12 September)
• Re: [w3c/payment-request] Some clarifications with Payment Request API (#774) (Wednesday, 12 September)
• Re: [w3c/payment-request] Some clarifications with Payment Request API (#774) (Tuesday, 11 September)
• Re: [w3c/payment-request] Some clarifications with Payment Request API (#774) (Tuesday, 11 September)

Addison Phillips

• Re: [w3c/payment-request] editorial: mark languageCode at risk (#764) (Wednesday, 5 September)

Adi

• Re: [w3c/payment-request] Some clarifications with Payment Request API (#774) (Tuesday, 11 September)
• Re: [w3c/payment-request] Some clarifications with Payment Request API (#774) (Tuesday, 11 September)
• Re: [w3c/payment-request] Some clarifications with Payment Request API (#774) (Tuesday, 11 September)
• Re: [w3c/payment-request] Some clarifications with Payment Request API (#774) (Tuesday, 11 September)
• Re: [w3c/payment-request] Some clarifications with Payment Request API (#774) (Tuesday, 11 September)
• Re: [w3c/payment-request] Some clarifications with Payment Request API (#774) (Tuesday, 11 September)
• Re: [w3c/payment-request] Some clarifications with Payment Request API (#774) (Tuesday, 11 September)
• [w3c/payment-request] Some clarifications with Payment Request API (#774) (Tuesday, 11 September)

Adrian Hope-Bailie

• Re: [w3c/payment-request] Remove PaymentAddress' languageCode (#765) (Thursday, 6 September)

aestes

• Re: [w3c/payment-request] Add MerchantValidationEvent.prototype.methodName (#776) (Wednesday, 12 September)
• Re: [w3c/payment-request] Some clarifications with Payment Request API (#774) (Tuesday, 11 September)
• Re: [w3c/payment-request] Some clarifications with Payment Request API (#774) (Tuesday, 11 September)
• Re: [w3c/payment-request] Remove PaymentAddress' languageCode (#765) (Tuesday, 4 September)

Akansha

• [w3c/payment-request] Issue #782 - Renames PayerErrorFields to PayerErrors (#789) (Sunday, 30 September)
• Re: [w3c/payment-request] Rename `PayerErrorFields` to be like `AddressErrors` and `BasicCardErrors` (#782) (Saturday, 29 September)

Bart

• Re: [w3c/payment-handler] How would iDeal work? (#251) (Wednesday, 19 September)

Christos Constantinou

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

Dave Longley

• Re: [w3c/payment-handler] [WIP] showPaymentUI() method (#325) (Monday, 24 September)
• Re: [w3c/payment-request] To address branded button issues and improve privacy, add browser support for payment method selection before the sheet (#777) (Thursday, 13 September)

Domenic Denicola

• Re: [w3c/payment-request] Add MerchantValidationEvent.prototype.methodName (#776) (Wednesday, 12 September)
• Re: [w3c/payment-method-basic-card] add BasicCardErrors (#58) (Monday, 10 September)

Eiji Kitamura

• Re: [w3c/payment-request] Some clarifications with Payment Request API (#774) (Thursday, 13 September)
• Re: [w3c/payment-request] Some clarifications with Payment Request API (#774) (Wednesday, 12 September)
• Re: [w3c/payment-request] Make billing address optional (#773) (Saturday, 8 September)
• [w3c/payment-request] Make billing address optional (#773) (Friday, 7 September)

Giorgio Tedesco

• Re: [w3c/payment-request] Add support for crypto currencies (#627) (Tuesday, 25 September)

Ian Clelland

• Re: [w3c/payment-request] Integration with Feature Policy (#600) (Friday, 14 September)
• Re: [w3c/payment-request] Integration with Feature Policy (#600) (Friday, 14 September)

ianbjacobs

• Re: [w3c/payment-method-id] Generate an implementation report (#54) (Sunday, 30 September)
• Re: [w3c/payment-request] Confirm tests and specs align (#779) (Sunday, 30 September)
• Re: [w3c/payment-handler] Code of Conduct (#326) (Wednesday, 26 September)
• Re: [w3c/payment-method-id] Generate an implementation report (#54) (Wednesday, 26 September)
• Re: [w3c/payment-method-id] Editorial: describe relationship to pay manifest (#53) (Wednesday, 26 September)
• Re: [w3c/payment-handler] [WIP] showPaymentUI() method (#325) (Monday, 24 September)
• Re: [w3c/webpayments-methods-tokenization] Add flow diagrams to the spec (#50) (Monday, 24 September)
• Re: [w3c/payment-request] To address branded button issues and improve privacy, add browser support for payment method selection before the sheet (#777) (Friday, 21 September)
• Re: [w3c/payment-request] Modifiers and [[serializedModifierData]] not actually used anywhere. (#753) (Friday, 21 September)
• Re: [w3c/payment-request] Define handling of multiple applicable modifiers (#684) (Friday, 21 September)
• [w3c/payment-method-basic-card] Define "last one wins" approach when Basic Card modifiers are equivalent (#60) (Friday, 21 September)
• [w3c/payment-method-basic-card] Drop supportedTypes? (#59) (Friday, 21 September)
• Re: [w3c/payment-request] Describe how to implement PaymentAddress.languageCode (#608) (Friday, 21 September)
• Re: [w3c/payment-handler] Remove link to issue 157 (#292) (Wednesday, 19 September)
• Re: [w3c/payment-handler] Remove link to issue 157 (#292) (Wednesday, 19 September)
• Re: [w3c/payment-handler] Remove requestPermission() (#277) (Wednesday, 19 September)
• Re: [w3c/payment-handler] How would iDeal work? (#251) (Wednesday, 19 September)
• Re: [w3c/payment-handler] Support for Abort() being delegated to Payment Handler (#117) (Wednesday, 19 September)
• Re: [w3c/payment-handler] (Editorial) Clarify validation expectation (#324) (Wednesday, 19 September)
• [w3c/payment-handler] (Editorial) Clarify validation expectation (#324) (Wednesday, 19 September)
• [w3c/payment-handler] (Editorial) fix storedInstrument per issue 316 (#323) (Wednesday, 19 September)
• Re: [w3c/payment-handler] Open Window Algorithm (#115) (Wednesday, 19 September)
• Re: [w3c/payment-handler] Open Window Algorithm (#115) (Wednesday, 19 September)
• Re: [w3c/payment-handler] How would iDeal work? (#251) (Wednesday, 19 September)
• Re: [w3c/payment-handler] How would iDeal work? (#251) (Wednesday, 19 September)
• Re: [w3c/payment-handler] Links to terms and common terminology (#50) (Wednesday, 19 September)
• Re: [w3c/payment-handler] Links to terms and common terminology (#50) (Wednesday, 19 September)
• [w3c/payment-handler] (Editorial) link fix for issue 317 (#322) (Wednesday, 19 September)
• Re: [w3c/payment-handler] Payment Handler window `.focused` field (#307) (Wednesday, 19 September)
• Re: [w3c/payment-handler] Payment Handler window `.focused` field (#307) (Wednesday, 19 September)
• [w3c/payment-handler] Update Open Window Algorithm (#321) (Wednesday, 19 September)
• [w3c/payment-handler] Added more security implementation notes from Rouslan; non-normative (#320) (Wednesday, 19 September)
• Re: [w3c/payment-handler] What mechanism allows enforcing payment handler authenticity? (#308) (Wednesday, 19 September)
• Re: [w3c/payment-handler] What mechanism allows enforcing payment handler authenticity? (#308) (Wednesday, 19 September)
• Re: [w3c/payment-request] Some clarifications with Payment Request API (#774) (Thursday, 13 September)
• Re: [w3c/payment-request] To address branded button issues and improve privacy, add browser support for payment method selection before the sheet (#777) (Wednesday, 12 September)
• Re: [w3c/payment-request] Some clarifications with Payment Request API (#774) (Wednesday, 12 September)
• [w3c/payment-request] To address branded button issues and improve privacy, add browser support for payment method selection before the sheet (#777) (Wednesday, 12 September)
• Re: [w3c/payment-handler] Notify merchant that payment method (possibly including the billing address) changed in payment handler. (#318) (Wednesday, 12 September)
• Re: [w3c/payment-handler] Notify merchant that payment method (possibly including the billing address) changed in payment handler. (#318) (Wednesday, 12 September)
• Re: [w3c/payment-handler] Review userHint (#273) (Wednesday, 12 September)
• Re: [w3c/payment-request] Some clarifications with Payment Request API (#774) (Wednesday, 12 September)
• Re: [w3c/payment-request] Some clarifications with Payment Request API (#774) (Wednesday, 12 September)
• Re: [w3c/payment-request] Some clarifications with Payment Request API (#774) (Tuesday, 11 September)
• Re: [w3c/payment-request] Some clarifications with Payment Request API (#774) (Tuesday, 11 September)
• Re: [w3c/payment-request] Some clarifications with Payment Request API (#774) (Tuesday, 11 September)
• [w3c/payment-request] Do we need to identify payment method in MerchantValidationEvent? (#775) (Tuesday, 11 September)
• Re: [w3c/payment-request] Some clarifications with Payment Request API (#774) (Tuesday, 11 September)
• Re: [w3c/payment-handler] Normative what happens when users closing the window opened by PaymentRequestEvent.openWindow (#299) (Tuesday, 11 September)
• Re: [w3c/payment-request] Some clarifications with Payment Request API (#774) (Tuesday, 11 September)
• [w3c/webpayments-methods-tokenization] Add more detail to cryptogram flows (#52) (Tuesday, 11 September)
• Re: [w3c/webpayments-methods-tokenization] Distinguish full tokenized-card from token-reference (lighter payment method) (#46) (Tuesday, 11 September)
• Re: [w3c/webpayments-methods-tokenization] Distinguish full tokenized-card from token-reference (lighter payment method) (#46) (Tuesday, 11 September)
• Re: [w3c/webpayments-methods-tokenization] What are the supportedCryptogramTypes? (#47) (Tuesday, 11 September)
• Re: [w3c/webpayments-methods-tokenization] What are the supportedCryptogramTypes? (#47) (Tuesday, 11 September)
• Re: [w3c/webpayments-methods-tokenization] Remove supportedCryptogramTypes (#49) (Tuesday, 11 September)
• Re: [w3c/webpayments-methods-tokenization] How are future card on file transactions supported through dynamic data? (#44) (Tuesday, 11 September)
• Re: [w3c/webpayments-methods-tokenization] How are future card on file transactions supported through dynamic data? (#44) (Tuesday, 11 September)
• Re: [w3c/webpayments-methods-tokenization] Distinguish full tokenized-card from token-reference (lighter payment method) (#46) (Monday, 10 September)
• Re: [w3c/webpayments-methods-tokenization] How are future card on file transactions supported through dynamic data? (#44) (Monday, 10 September)
• Re: [w3c/payment-request] Extract actionable items from Shopify study (#772) (Friday, 7 September)
• Re: [w3c/payment-handler] PaymentManager behavior unclear (#253) (Thursday, 6 September)
• Re: [w3c/payment-request] Remove PaymentAddress' languageCode (#765) (Thursday, 6 September)

Jake Archibald

• Re: [w3c/payment-handler] Simplifying functional event handling (#305) (Thursday, 20 September)
• Re: [w3c/payment-handler] Simplifying functional event handling (#305) (Friday, 7 September)

Jinho Bang

• Re: [w3c/payment-handler] [WIP] showPaymentUI() method (#325) (Thursday, 27 September)
• Re: [w3c/payment-handler] [WIP] showPaymentUI() method (#325) (Monday, 24 September)
• [w3c/payment-handler] [WIP] showPaymentUI() method (#325) (Monday, 24 September)
• Re: [w3c/payment-handler] Update Example6 and Example7 (#290) (Thursday, 20 September)
• Re: [w3c/payment-handler] Suggest changing a shape of openWindow() (#300) (Thursday, 20 September)
• Re: [w3c/payment-request] Add paymentMethodErrors, payerErrors, to PaymentDetailsUpdate (#768) (Saturday, 15 September)
• Re: [w3c/payment-handler] Suggest changing a shape of openWindow() (#300) (Friday, 14 September)
• Re: [w3c/payment-handler] Notify merchant that payment method (possibly including the billing address) changed in payment handler. (#318) (Friday, 14 September)
• Re: [w3c/payment-handler] Suggest changing a shape of openWindow() (#300) (Thursday, 13 September)
• Re: [w3c/payment-handler] Notify merchant that payment method (possibly including the billing address) changed in payment handler. (#318) (Thursday, 13 September)
• Re: [w3c/payment-request] Add paymentMethodErrors, payerErrors, to PaymentDetailsUpdate (#768) (Thursday, 13 September)
• Re: [w3c/payment-request] Add MerchantValidationEvent.prototype.methodName (#776) (Thursday, 13 September)
• Re: [w3c/payment-request] Make billing address optional (#773) (Friday, 7 September)
• Re: [w3c/payment-request] Add paymentMethodErrors, payerErrors, to PaymentDetailsUpdate (#768) (Monday, 3 September)

Jonas Mendes

• Re: [w3c/payment-handler] PaymentManager behavior unclear (#253) (Friday, 7 September)
• Re: [w3c/payment-handler] PaymentManager behavior unclear (#253) (Thursday, 6 September)

Krystian Czesak

• Re: [w3c/payment-request] To address branded button issues and improve privacy, add browser support for payment method selection before the sheet (#777) (Friday, 21 September)
• Re: [w3c/payment-request] To address branded button issues and improve privacy, add browser support for payment method selection before the sheet (#777) (Friday, 21 September)
• Re: [w3c/payment-request] To address branded button issues and improve privacy, add browser support for payment method selection before the sheet (#777) (Monday, 17 September)
• Re: [w3c/payment-request] To address branded button issues and improve privacy, add browser support for payment method selection before the sheet (#777) (Monday, 17 September)

Luna Lu

• Re: [w3c/payment-request] Integration with Feature Policy (#600) (Friday, 14 September)

Marcos Cáceres

• Re: [w3c/payment-request] Confirm tests and specs align (#779) (Sunday, 30 September)
• [w3c/payment-method-id] Prepare for Proposed Recommendation (#56) (Sunday, 30 September)
• Re: [w3c/payment-method-id] Generate an implementation report (#54) (Sunday, 30 September)
• Re: [w3c/payment-method-id] Updated the link to the test-suit (#55) (Sunday, 30 September)
• Re: [w3c/payment-request] Rename `PayerErrorFields` to be like `AddressErrors` and `BasicCardErrors` (#782) (Saturday, 29 September)
• Re: [w3c/payment-request] Fix the links to the `data-tests` in the spec (#787) (Friday, 28 September)
• Re: [w3c/payment-request] Fix #787 : Fix the links to the `data-tests` in the spec (#788) (Friday, 28 September)
• Re: [w3c/payment-request] Fix #787 : Fix the links to the `data-tests` in the spec (#788) (Friday, 28 September)
• Re: [w3c/payment-request] Fix #787 : Fix the links to the `data-tests` in the spec (#788) (Friday, 28 September)
• Re: [w3c/payment-request] fix: give dictionary members sensible defaults (#781) (Friday, 28 September)
• Re: [w3c/payment-request] fix: give dictionary members sensible defaults (#781) (Friday, 28 September)
• Re: [w3c/payment-request] "data-test" should be changed to "data-tests" in spec (#785) (Friday, 28 September)
• Re: [w3c/payment-request] "data-test" should be changed to "data-tests" in spec (#785) (Friday, 28 September)
• Re: [w3c/payment-request] Fix #785 : data-test should be changed to data-tests in spec (#786) (Friday, 28 September)
• Re: [w3c/payment-request] Fix #785 : data-test should be changed to data-tests in spec (#786) (Friday, 28 September)
• Re: [w3c/payment-request] Fix #785 : data-test should be changed to data-tests in spec (#786) (Friday, 28 September)
• Re: [w3c/payment-method-id] Updated the link to the test-suit (#55) (Friday, 28 September)
• Re: [w3c/payment-request] Fix #779 : Confirm test and specs align (#784) (Friday, 28 September)
• Re: [w3c/payment-request] Fix #779 : Confirm test and specs align (#784) (Friday, 28 September)
• Re: [w3c/payment-method-id] Updated the link to the test-suit (#55) (Friday, 28 September)
• Re: [w3c/payment-method-id] Updated the link to the test-suit (#55) (Thursday, 27 September)
• Re: [w3c/payment-method-id] Updated the link to the test-suit (#55) (Thursday, 27 September)
• Re: [w3c/payment-method-id] Updated the link to the test-suit (#55) (Thursday, 27 September)
• Re: [w3c/payment-method-id] Updated the link to the test-suit (#55) (Thursday, 27 September)
• Re: [w3c/payment-method-id] Generate an implementation report (#54) (Thursday, 27 September)
• Re: [w3c/payment-request] Editorial: fix link to basic card error dictionary in examples (#783) (Thursday, 27 September)
• Re: [w3c/payment-request] Fix link to basic card error dictionary in examples (#783) (Thursday, 27 September)
• Re: [w3c/payment-request] Fix link to basic card error dictionary in examples (#783) (Thursday, 27 September)
• Re: [w3c/payment-request] Rename `PayerErrorFields` to be like `AddressErrors` and `BasicCardErrors` (#782) (Thursday, 27 September)
• Re: [w3c/payment-method-id] Generate an implementation report (#54) (Wednesday, 26 September)
• Re: [w3c/payment-method-id] Generate an implementation report (#54) (Wednesday, 26 September)
• Re: [w3c/payment-method-id] Generate an implementation report (#54) (Wednesday, 26 September)
• Re: [w3c/payment-method-id] Generate an implementation report (#54) (Wednesday, 26 September)
• Re: [w3c/payment-method-id] Generate an implementation report (#54) (Wednesday, 26 September)
• Re: [w3c/payment-method-id] Generate an implementation report (#54) (Wednesday, 26 September)
• Re: [w3c/payment-method-id] Generate an implementation report (#54) (Wednesday, 26 September)
• Re: [w3c/payment-method-id] Editorial: describe relationship to pay manifest (#53) (Wednesday, 26 September)
• Re: [w3c/payment-method-id] What can I do with a URL-based payment method identifier? (#52) (Wednesday, 26 September)
• [w3c/payment-request] fix: give dictionary member sensible defaults (#781) (Wednesday, 26 September)
• [w3c/payment-request] Sensible defaults for dictionary members (#780) (Wednesday, 26 September)
• [w3c/payment-request] Confirm test and specs align (#779) (Wednesday, 26 September)
• [w3c/payment-method-id] Generate an implementation report (#54) (Wednesday, 26 September)
• Re: [w3c/payment-method-id] Editorial: describe relationship to pay manifest (#53) (Wednesday, 26 September)
• [w3c/payment-method-id] Editorial: describe relationship to pay manifest (#53) (Wednesday, 26 September)
• Re: [w3c/payment-method-basic-card] Signaling payment handler details errors (#57) (Thursday, 20 September)
• Re: [w3c/payment-method-basic-card] add BasicCardErrors (#58) (Thursday, 20 September)
• Re: [w3c/payment-method-basic-card] User changes payment method (#53) (Thursday, 20 September)
• Re: [w3c/payment-handler] Simplifying functional event handling (#305) (Thursday, 20 September)
• Re: [w3c/payment-request] Add paymentMethodErrors, payerErrors, to PaymentDetailsUpdate (#768) (Wednesday, 19 September)
• Re: [w3c/payment-request] PaymentDetailsUpdate needs to include payerErrors (#766) (Wednesday, 19 September)
• Re: [w3c/payment-request] Add paymentMethodErrors, payerErrors, to PaymentDetailsUpdate (#768) (Wednesday, 19 September)
• Re: [w3c/payment-request] Not able to add shipping options dynamically for apple pay (#778) (Tuesday, 18 September)
• Re: [w3c/payment-request] Not able to add shipping options dynamically for apple pay (#778) (Tuesday, 18 September)
• Re: [w3c/payment-request] Not able to add shipping options dynamically for apple pay (#778) (Tuesday, 18 September)
• Re: [w3c/payment-request] Not able to add shipping options dynamically for apple pay (#778) (Tuesday, 18 September)
• Re: [w3c/payment-request] Integration with Feature Policy (#600) (Monday, 17 September)
• Re: [w3c/payment-request] Integration with Feature Policy (#600) (Monday, 17 September)
• Re: [w3c/payment-handler] Fix Web IDL typo: bool → boolean (#319) (Saturday, 15 September)
• Re: [w3c/payment-handler] Fix Web IDL typo: bool → boolean (#319) (Saturday, 15 September)
• Re: [w3c/payment-request] Integration with Feature Policy (#600) (Friday, 14 September)
• Re: [w3c/payment-request] Integration with Feature Policy (#600) (Friday, 14 September)
• Re: [w3c/payment-request] Add paymentMethodErrors, payerErrors, to PaymentDetailsUpdate (#768) (Thursday, 13 September)
• Re: [w3c/payment-request] Add paymentMethodErrors, payerErrors, to PaymentDetailsUpdate (#768) (Thursday, 13 September)
• Re: [w3c/payment-request] Add paymentMethodErrors, payerErrors, to PaymentDetailsUpdate (#768) (Thursday, 13 September)
• Re: [w3c/payment-request] Some clarifications with Payment Request API (#774) (Thursday, 13 September)
• Re: [w3c/payment-request] Some clarifications with Payment Request API (#774) (Thursday, 13 September)
• Re: [w3c/payment-request] Some clarifications with Payment Request API (#774) (Thursday, 13 September)
• Re: [w3c/payment-request] Add MerchantValidationEvent.prototype.methodName (#776) (Thursday, 13 September)
• Re: [w3c/payment-request] Do we need to identify payment method in MerchantValidationEvent? (#775) (Thursday, 13 September)
• Re: [w3c/payment-request] Add MerchantValidationEvent.prototype.methodName (#776) (Thursday, 13 September)
• Re: [w3c/payment-request] Add MerchantValidationEvent.prototype.methodName (#776) (Thursday, 13 September)
• Re: [w3c/payment-request] Add MerchantValidationEvent.prototype.methodName (#776) (Thursday, 13 September)
• Re: [w3c/payment-request] Add MerchantValidationEvent.prototype.methodName (#776) (Thursday, 13 September)
• Re: [w3c/payment-request] Add MerchantValidationEvent.prototype.methodName (#776) (Wednesday, 12 September)
• Re: [w3c/payment-request] Add MerchantValidationEvent.prototype.methodName (#776) (Wednesday, 12 September)
• Re: [w3c/payment-request] Add MerchantValidationEvent.prototype.methodName (#776) (Wednesday, 12 September)
• [w3c/payment-request] Add MerchantValidationEvent.prototype.methodName (#776) (Wednesday, 12 September)
• Re: [w3c/payment-request] Define PaymentResponse.retry() method (#715) (Tuesday, 11 September)
• Re: [w3c/payment-method-basic-card] add BasicCardErrors (#58) (Monday, 10 September)
• Re: [w3c/payment-request] Remove PaymentAddress' languageCode (#765) (Saturday, 8 September)
• Re: [w3c/payment-request] Make billing address optional (#773) (Friday, 7 September)
• Re: [w3c/payment-request] Make billing address optional (#773) (Friday, 7 September)
• [w3c/payment-request] Extract actionable items from Shopify study (#772) (Friday, 7 September)
• Re: [w3c/payment-request] Remove PaymentAddress' languageCode (#765) (Thursday, 6 September)
• Re: [w3c/payment-request] editorial: mark languageCode at risk (#764) (Thursday, 6 September)
• Re: [w3c/payment-request] editorial: mark languageCode at risk (#764) (Wednesday, 5 September)
• Re: [w3c/payment-request] editorial: mark languageCode at risk (#764) (Wednesday, 5 September)
• Re: [w3c/payment-request] Add link to SecureContext test (#697) (Wednesday, 5 September)
• Re: [w3c/payment-request] Populate implementation report (#560) (Wednesday, 5 September)
• Re: [w3c/payment-request] Populate implementation report (#560) (Wednesday, 5 September)
• Re: [w3c/payment-request] fix: give PaymentMethodChangeEventInit defaults (#771) (Tuesday, 4 September)
• Re: [w3c/payment-request] Can PaymentMethodChangeEventInit really have a required member? (#770) (Tuesday, 4 September)
• Re: [w3c/payment-request] fix: give PaymentMethodChangeEventInit defaults (#771) (Tuesday, 4 September)
• Re: [w3c/payment-request] fix: give PaymentMethodChangeEventInit defaults (#771) (Tuesday, 4 September)
• Re: [w3c/payment-request] Add paymentMethodErrors, payerErrors, to PaymentDetailsUpdate (#768) (Tuesday, 4 September)
• Re: [w3c/payment-request] Remove PaymentAddress' languageCode (#765) (Tuesday, 4 September)

Matt N.

• [w3c/payment-request] Fix link to basic card error dictionary in examples (#783) (Thursday, 27 September)
• [w3c/payment-request] Rename `PayerErrorFields` to be like `AddressErrors` and `BasicCardErrors` (#782) (Thursday, 27 September)

Ms2ger

• [w3c/payment-handler] Link for "fetching image object" is broken (#317) (Wednesday, 12 September)
• [w3c/payment-handler] Examples involving storedInstrument seem broken (#316) (Wednesday, 12 September)

Peter Saint-Andre

• [w3c/webpayments-methods-tokenization] Better orient the reader (#51) (Tuesday, 11 September)
• [w3c/webpayments-methods-tokenization] Add flow diagrams to the spec (#50) (Tuesday, 11 September)
• Re: [w3c/webpayments-methods-tokenization] How are future card on file transactions supported through dynamic data? (#44) (Tuesday, 11 September)
• Re: [w3c/webpayments-methods-tokenization] Remove supportedCryptogramTypes (#49) (Tuesday, 11 September)
• Re: [w3c/payment-request] Describe how to implement PaymentAddress.languageCode (#608) (Thursday, 6 September)
• Re: [w3c/payment-request] editorial: mark languageCode at risk (#764) (Wednesday, 5 September)
• Re: [w3c/payment-request] editorial: mark languageCode at risk (#764) (Wednesday, 5 September)
• Re: [w3c/payment-request] editorial: mark languageCode at risk (#764) (Wednesday, 5 September)

Philip Jägenstedt

• Re: [w3c/payment-handler] Notify merchant that payment method (possibly including the billing address) changed in payment handler. (#318) (Tuesday, 18 September)
• [w3c/payment-handler] Fix Web IDL typo: bool → boolean (#319) (Saturday, 15 September)
• Re: [w3c/payment-handler] Notify merchant that payment method (possibly including the billing address) changed in payment handler. (#318) (Saturday, 15 September)
• Re: [w3c/payment-handler] Notify merchant that payment method (possibly including the billing address) changed in payment handler. (#318) (Saturday, 15 September)

Philippe Le Hegaret

• Re: [w3c/payment-handler] Code of Conduct (#326) (Wednesday, 26 September)
• [w3c/payment-handler] Code of Conduct (#326) (Wednesday, 26 September)

pumbapark21

• Re: [w3c/payment-request] Add paymentMethodErrors, payerErrors, to PaymentDetailsUpdate (dbd585f) (Monday, 17 September)

Rouslan Solomakhin

• Re: [w3c/payment-handler] [WIP] showPaymentUI() method (#325) (Thursday, 27 September)
• Re: [w3c/payment-handler] [WIP] showPaymentUI() method (#325) (Monday, 24 September)
• Re: [w3c/payment-handler] [WIP] showPaymentUI() method (#325) (Monday, 24 September)
• Re: [w3c/payment-handler] Simplifying functional event handling (#305) (Wednesday, 19 September)
• Re: [w3c/payment-handler] Simplifying functional event handling (#305) (Wednesday, 19 September)
• Re: [w3c/payment-handler] Update Example6 and Example7 (#290) (Wednesday, 19 September)
• Re: [w3c/payment-handler] Cross-origin iframes and feature policy. (#282) (Wednesday, 19 September)
• Re: [w3c/payment-handler] Cross-origin iframes and feature policy. (#282) (Wednesday, 19 September)
• Re: [w3c/payment-handler] Remove requestPermission() (#277) (Wednesday, 19 September)
• Re: [w3c/payment-handler] Proposal: Remove requestPermission() (#246) (Wednesday, 19 September)
• Re: [w3c/payment-handler] Remove requestPermission() (#277) (Wednesday, 19 September)
• Re: [w3c/payment-handler] Remove requestPermission() (#277) (Wednesday, 19 September)
• Re: [w3c/payment-handler] Only allows instrument.set() in active service worker (#224) (Wednesday, 19 September)
• Re: [w3c/payment-handler] Add AbortPaymentEvent. (#207) (Wednesday, 19 September)
• Re: [w3c/payment-handler] Add AbortPaymentEvent. (#207) (Wednesday, 19 September)
• Re: [w3c/payment-handler] (Editorial) Clarify validation expectation (#324) (Wednesday, 19 September)
• Re: [w3c/payment-handler] What should payees validate? (#310) (Wednesday, 19 September)
• Re: [w3c/payment-handler] (Editorial) Clarify validation expectation (#324) (Wednesday, 19 September)
• Re: [w3c/payment-handler] (Editorial) fix storedInstrument per issue 316 (#323) (Wednesday, 19 September)
• Re: [w3c/payment-handler] Examples involving storedInstrument seem broken (#316) (Wednesday, 19 September)
• Re: [w3c/payment-handler] (Editorial) fix storedInstrument per issue 316 (#323) (Wednesday, 19 September)
• Re: [w3c/payment-handler] (Editorial) link fix for issue 317 (#322) (Wednesday, 19 September)
• Re: [w3c/payment-handler] Link for "fetching image object" is broken (#317) (Wednesday, 19 September)
• Re: [w3c/payment-handler] (Editorial) link fix for issue 317 (#322) (Wednesday, 19 September)
• Re: [w3c/payment-handler] Payment Handler window `.focused` field (#307) (Wednesday, 19 September)
• Re: [w3c/payment-handler] Added more security implementation notes from Rouslan; non-normative (#320) (Wednesday, 19 September)
• Re: [w3c/payment-handler] Added more security implementation notes from Rouslan; non-normative (#320) (Wednesday, 19 September)
• Re: [w3c/payment-handler] Suggest changing a shape of openWindow() (#300) (Wednesday, 19 September)
• Re: [w3c/payment-handler] Fix Web IDL typo: bool → boolean (#319) (Monday, 17 September)
• Re: [w3c/payment-handler] Notify merchant that payment method (possibly including the billing address) changed in payment handler. (#318) (Monday, 17 September)
• Re: [w3c/payment-request] Integration with Feature Policy (#600) (Friday, 14 September)
• Re: [w3c/payment-request] Integration with Feature Policy (#600) (Friday, 14 September)
• Re: [w3c/payment-handler] Add support for communicating billing address to merchant (e.g., for VAT computation) (#314) (Friday, 14 September)
• Re: [w3c/payment-handler] Notify merchant that payment method (possibly including the billing address) changed in payment handler. (#318) (Friday, 14 September)
• Re: [w3c/payment-handler] Suggest changing a shape of openWindow() (#300) (Friday, 14 September)
• Re: [w3c/payment-handler] Notify merchant that payment method (possibly including the billing address) changed in payment handler. (#318) (Thursday, 13 September)
• Re: [w3c/payment-handler] Notify merchant that payment method (possibly including the billing address) changed in payment handler. (#318) (Thursday, 13 September)
• Re: [w3c/payment-handler] Suggest changing a shape of openWindow() (#300) (Thursday, 13 September)
• Re: [w3c/payment-handler] Notify merchant that payment method (possibly including the billing address) changed in payment handler. (#318) (Wednesday, 12 September)
• Re: [w3c/payment-handler] Notify merchant that payment method (possibly including the billing address) changed in payment handler. (#318) (Wednesday, 12 September)
• Re: [w3c/payment-handler] Notify merchant that payment method (possibly including the billing address) changed in payment handler. (#318) (Wednesday, 12 September)
• Re: [w3c/payment-request] Support requesting billing address (#749) (Wednesday, 12 September)
• [w3c/payment-handler] Change payment method (#318) (Wednesday, 12 September)
• Re: [w3c/payment-handler] Review userHint (#273) (Wednesday, 12 September)
• Re: [w3c/payment-handler] Drop PaymentInstrument in favor of MethodCapability (#302) (Wednesday, 12 September)
• Re: [w3c/payment-request] Add MerchantValidationEvent.prototype.methodName (#776) (Wednesday, 12 September)
• Re: [w3c/payment-request] Some clarifications with Payment Request API (#774) (Tuesday, 11 September)
• Re: [w3c/payment-handler] Suggest changing a shape of openWindow() (#300) (Tuesday, 11 September)
• Re: [w3c/payment-handler] Normative what happens when users closing the window opened by PaymentRequestEvent.openWindow (#299) (Tuesday, 11 September)
• Re: [w3c/payment-handler] PaymentManager behavior unclear (#253) (Friday, 7 September)
• Re: [w3c/payment-handler] Simplifying functional event handling (#305) (Friday, 7 September)
• Re: [w3c/payment-handler] Simplifying functional event handling (#305) (Friday, 7 September)
• Re: [w3c/payment-handler] Simplifying functional event handling (#305) (Friday, 7 September)
• Re: [w3c/payment-handler] Simplifying functional event handling (#305) (Friday, 7 September)
• Re: [w3c/payment-handler] Simplifying functional event handling (#305) (Friday, 7 September)
• Re: [w3c/payment-handler] PaymentManager behavior unclear (#253) (Thursday, 6 September)
• Re: [w3c/payment-handler] PaymentManager behavior unclear (#253) (Thursday, 6 September)

Siddeshwaraswamy

• Re: [w3c/payment-request] Not able to add shipping options dynamically for apple pay (#778) (Tuesday, 18 September)
• Re: [w3c/payment-request] Not able to add shipping options dynamically for apple pay (#778) (Tuesday, 18 September)
• Re: [w3c/payment-request] Not able to add shipping options dynamically for apple pay (#778) (Tuesday, 18 September)
• [w3c/payment-request] Not able to add shipping options for apple pay (#778) (Tuesday, 18 September)

Sylvia Mittal

• Re: [w3c/payment-request] Confirm tests and specs align (#779) (Sunday, 30 September)
• Re: [w3c/payment-request] Fix #787 : Fix the links to the `data-tests` in the spec (#788) (Friday, 28 September)
• Re: [w3c/payment-request] Confirm tests and specs align (#779) (Friday, 28 September)
• [w3c/payment-request] Fix #787 : Fix the links to the `data-tests` in the spec (#788) (Friday, 28 September)
• [w3c/payment-request] Fix the links to the `data-tests` in the spec (#787) (Friday, 28 September)
• [w3c/payment-request] Fix #785 : data-test should be changed to data-tests in spec (#786) (Friday, 28 September)
• [w3c/payment-request] "data-test" should be changed to "data-tests" in spec (#785) (Friday, 28 September)
• [w3c/payment-request] Fix #779 : Confirm test and specs align (#784) (Thursday, 27 September)
• Re: [w3c/payment-request] Confirm test and specs align (#779) (Wednesday, 26 September)

Veikko Eeva

• Re: [w3c/payment-request] support of VAT (#699) (Friday, 21 September)

Yatri Patel

• Re: [w3c/payment-method-id] Updated the link to the test-suit (#55) (Sunday, 30 September)
• Re: [w3c/payment-method-id] Updated the link to the test-suit (#55) (Sunday, 30 September)
• Re: [w3c/payment-method-id] Updated the link to the test-suit (#55) (Friday, 28 September)
• Re: [w3c/payment-method-id] Generate an implementation report (#54) (Friday, 28 September)
• Re: [w3c/payment-method-id] Updated the link to the test-suit (#55) (Thursday, 27 September)
• Re: [w3c/payment-method-id] Updated the link to the test-suit (#55) (Thursday, 27 September)
• Re: [w3c/payment-method-id] Updated the link to the test-suit (#55) (Thursday, 27 September)
• Re: [w3c/payment-method-id] Updated the link to the test-suit (#55) (Thursday, 27 September)
• [w3c/payment-method-id] Updated the link to the test-suit (#55) (Thursday, 27 September)
• Re: [w3c/payment-method-id] Generate an implementation report (#54) (Thursday, 27 September)
• Re: [w3c/payment-method-id] Generate an implementation report (#54) (Wednesday, 26 September)
• Re: [w3c/payment-method-id] Generate an implementation report (#54) (Wednesday, 26 September)
• Re: [w3c/payment-method-id] Generate an implementation report (#54) (Wednesday, 26 September)
• Re: [w3c/payment-method-id] Generate an implementation report (#54) (Wednesday, 26 September)
• Re: [w3c/payment-method-id] Generate an implementation report (#54) (Wednesday, 26 September)
• Re: [w3c/payment-method-id] Generate an implementation report (#54) (Wednesday, 26 September)
• Re: [w3c/payment-method-id] Generate an implementation report (#54) (Wednesday, 26 September)

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