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

Friday, 31 August 2018

• Re: [w3c/webpayments-methods-tokenization] What are the supportedCryptogramTypes? (#47) ianbjacobs
• Re: [w3c/payment-request] fix: give PaymentMethodChangeEventInit defaults (#771) Marcos Cáceres
• Re: [w3c/payment-request] fix: default methodName to empty string (#771) Marcos Cáceres

Thursday, 30 August 2018

• Re: [w3c/payment-request] Add support for merchant validation (#646) Marcos Cáceres
• Re: [w3c/payment-request] Add support for merchant validation (#751) Marcos Cáceres
• Re: [w3c/payment-request] Add support for merchant validation (#751) Domenic Denicola
• Re: [w3c/payment-request] fix: default methodName to empty string (#771) Domenic Denicola
• Re: [w3c/payment-request] fix: default methodName to empty string (#771) aestes
• Re: [w3c/payment-request] fix: default methodName to empty string (#771) aestes
• Re: [w3c/payment-request] fix: default methodName to empty string (#771) Marcos Cáceres
• [w3c/payment-request] fix: default methodName to empty string (#771) Marcos Cáceres
• Re: [w3c/payment-request] Can PaymentMethodChangeEventInit really have a required member? (#770) Domenic Denicola
• Re: [w3c/payment-request] Can PaymentMethodChangeEventInit really have a required member? (#770) Marcos Cáceres
• Re: [w3c/payment-request] Can PaymentMethodChangeEventInit really have a required member? (#770) Chris Dumez
• Re: [w3c/payment-request] Can PaymentMethodChangeEventInit really have a required member? (#770) Chris Dumez
• [w3c/payment-request] Can PaymentMethodChangeEventInit really have a required member? (#770) Chris Dumez
• Re: [w3c/payment-request] Section 3.11 (onpaymentmethodchange attribute) mentions the wrong event interface (#769) Marcos Cáceres
• Re: [w3c/payment-request] Section 3.11 (onpaymentmethodchange attribute) mentions the wrong event interface (#769) Marcos Cáceres
• [w3c/payment-request] Section 3.11 (onpaymentmethodchange attribute) mentions the wrong event interface (#769) aestes

Wednesday, 29 August 2018

• Re: [w3c/payment-request] Add support for merchant validation (#751) Marcos Cáceres
• Re: [w3c/payment-request] Add support for merchant validation (#751) Marcos Cáceres
• Re: [w3c/payment-request] Add support for merchant validation (#751) Marcos Cáceres

Tuesday, 28 August 2018

• 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] Support requesting billing address (#749) Marcos Cáceres
• Re: [w3c/webpayments-methods-tokenization] What are the supportedCryptogramTypes? (#47) ianbjacobs
• [w3c/webpayments-methods-tokenization] Remove supportedCryptogramTypes (#49) ianbjacobs
• Re: [w3c/payment-handler] Remove modifiers from CanMakePaymentEvent. (#315) Rouslan Solomakhin
• Re: [w3c/payment-handler] Remove modifiers from CanMakePaymentEvent? (#289) Rouslan Solomakhin
• Re: [w3c/payment-request] Add support for merchant validation (#751) Domenic Denicola
• Re: [w3c/payment-handler] Remove modifiers from CanMakePaymentEvent. (#315) Jinho Bang
• Re: [w3c/payment-request] Modifiers and [[serializedModifierData]] not actually used anywhere. (#753) Rouslan Solomakhin
• Re: [w3c/payment-request] Modifiers and [[serializedModifierData]] not actually used anywhere. (#753) ianbjacobs
• Re: [w3c/payment-request] Add paymentMethodErrors, payerErrors, to PaymentDetailsUpdate (#768) Jinho Bang
• Re: [w3c/payment-request] Add support for merchant validation (#751) Marcos Cáceres
• Re: [w3c/payment-request] Should API support billing address capture (for tax computation)? (#27) Marcos Cáceres
• Re: [w3c/payment-request] Should API support billing address capture (for tax computation)? (#27) Marcos Cáceres
• Re: [w3c/payment-request] Add paymentMethodErrors, payerErrors, to PaymentDetailsUpdate (#768) Marcos Cáceres
• [w3c/payment-request] Add paymentMethodErrors, payerErrors, to PaymentDetailsUpdate (#768) Marcos Cáceres
• Re: [w3c/payment-request] Add support for merchant validation (#751) Marcos Cáceres
• Re: [w3c/payment-request] Add support for merchant validation (#751) Marcos Cáceres
• Re: [w3c/payment-request] Add support for merchant validation (#751) Marcos Cáceres
• [w3c/payment-request] Update spec to use "event constructing steps" (#767) Marcos Cáceres
• Re: [w3c/payment-request] Add support for merchant validation (#751) Marcos Cáceres
• Re: [w3c/payment-request] Add support for merchant validation (#751) Marcos Cáceres
• Re: [w3c/payment-request] Add support for merchant validation (#751) Marcos Cáceres
• Re: [w3c/payment-request] Add support for merchant validation (#751) Marcos Cáceres
• Re: [w3c/payment-request] Modifiers and [[serializedModifierData]] not actually used anywhere. (#753) Marcos Cáceres
• Re: [w3c/payment-request] Remove PaymentAddress' languageCode (#765) Marcos Cáceres
• Re: [w3c/payment-request] Remove PaymentAddress' languageCode (#765) Rouslan Solomakhin

Monday, 27 August 2018

• Re: [w3c/payment-request] Remove PaymentAddress' languageCode (#765) Marcos Cáceres
• Re: [w3c/payment-request] Modifiers and [[serializedModifierData]] not actually used anywhere. (#753) Krystian Czesak
• Re: [w3c/payment-handler] Remove modifiers from CanMakePaymentEvent. (#315) ianbjacobs
• Re: [w3c/payment-handler] Remove modifiers from CanMakePaymentEvent. (#315) Rouslan Solomakhin
• Re: [w3c/payment-handler] Remove modifiers from CanMakePaymentEvent. (#315) ianbjacobs
• [w3c/payment-handler] Remove modifiers from CanMakePaymentEvent. (#315) Rouslan Solomakhin
• Re: [w3c/payment-request] Remove PaymentAddress' languageCode (#765) Rouslan Solomakhin
• Re: [w3c/payment-request] Remove PaymentAddress' languageCode (#765) Rouslan Solomakhin
• Re: [w3c/payment-request] Remove PaymentAddress' languageCode (#765) Marcos Cáceres
• Re: [w3c/payment-request] Add support for merchant validation (#751) Marcos Cáceres
• [w3c/payment-request] PaymentDetailsUpdate needs to include payerErrors (#766) Marcos Cáceres
• Re: [w3c/payment-request] Remove PaymentAddress' languageCode (#765) Marcos Cáceres
• Re: [w3c/payment-request] Support requesting billing address (#749) Marcos Cáceres
• Re: [w3c/payment-request] Modifiers and [[serializedModifierData]] not actually used anywhere. (#753) Marcos Cáceres
• [w3c/payment-request] Remove PaymentAddress' languageCode (#765) Marcos Cáceres
• Re: [w3c/payment-request] editorial: mark languageCode at risk (#764) Marcos Cáceres
• Re: [w3c/payment-request] editorial: mark languageCode at risk (#764) Marcos Cáceres
• Re: [w3c/payment-request] editorial: mark languageCode at risk (#764) Marcos Cáceres

Friday, 24 August 2018

• Re: [w3c/payment-request] Support requesting billing address (#749) Adrian Hope-Bailie
• Re: [w3c/payment-request] Support requesting billing address (#749) Rouslan Solomakhin
• Re: [w3c/payment-request] Support requesting billing address (#749) Adrian Hope-Bailie
• Re: [w3c/payment-request] Modifiers and [[serializedModifierData]] not actually used anywhere. (#753) ianbjacobs
• Re: [w3c/payment-request] Mark languageCode at risk (#764) Peter Saint-Andre
• Re: [w3c/payment-request] Mark languageCode at risk (#764) Rouslan Solomakhin
• Re: [w3c/payment-request] Support requesting billing address (#749) Rouslan Solomakhin
• Re: [w3c/payment-request] Mark languageCode at risk (#764) ianbjacobs
• Re: [w3c/payment-request] Support requesting billing address (#749) Marcos Cáceres
• Re: [w3c/payment-request] Support requesting billing address (#749) Marcos Cáceres
• Re: [w3c/payment-request] Support requesting billing address (#749) Marcos Cáceres
• Re: [w3c/payment-request] Support requesting billing address (#749) Marcos Cáceres
• Re: [w3c/payment-request] Mark languageCode at risk (#764) Marcos Cáceres
• Re: [w3c/payment-request] Mark languageCode at risk (#764) Marcos Cáceres
• Re: [w3c/payment-request] Mark languageCode at risk (#764) Marcos Cáceres
• [w3c/payment-request] Mark languageCode at risk (#764) Marcos Cáceres
• Re: [w3c/payment-request] Modifiers and [[serializedModifierData]] not actually used anywhere. (#753) Marcos Cáceres

Thursday, 23 August 2018

• Re: [w3c/payment-request] Modifiers and [[serializedModifierData]] not actually used anywhere. (#753) Peter Saint-Andre
• Re: [w3c/payment-request] Support payment method errors (#749) Marcos Cáceres
• Re: [w3c/payment-request] Add support for merchant validation (#751) Domenic Denicola
• Re: [w3c/payment-request] Describe how to implement PaymentAddress.languageCode (#608) Peter Saint-Andre
• Re: [w3c/payment-request] Support payment method errors (#749) Peter Saint-Andre
• Re: [w3c/payment-request] Support payment method errors (#749) Marcos Cáceres

Wednesday, 22 August 2018

• Re: [w3c/payment-request] Support payment method errors (#749) Peter Saint-Andre
• Re: [w3c/payment-request] Support payment method errors (#749) Adam Solove
• Re: [w3c/3ds] Mixing 3DS with Payment Methods (#9) ianbjacobs
• Re: [w3c/3ds] Mixing 3DS with Payment Methods (#9) Peter Saint-Andre
• Re: [w3c/3ds] Mixing 3DS with Payment Methods (#9) ianbjacobs
• Re: [w3c/3ds] Mixing 3DS with Payment Methods (#9) Peter Saint-Andre
• Re: [w3c/3ds] Mixing 3DS with Payment Methods (#9) ianbjacobs
• Re: [w3c/3ds] Mixing 3DS with Payment Methods (#9) Manu Sporny
• Re: [w3c/3ds] Mixing 3DS with Payment Methods (#9) Peter Saint-Andre
• Re: [w3c/3ds] Mixing 3DS with Payment Methods (#9) ianbjacobs
• [w3c/3ds] Mixing 3DS with Payment Methods (#9) Peter Saint-Andre
• [w3c/3ds] Spec feedback (#8) Adam Solove
• Re: [w3c/payment-request] Modifiers and [[serializedModifierData]] not actually used anywhere. (#753) Nick Telford-Reed

Tuesday, 21 August 2018

• Re: [w3c/payment-request] Add support for merchant validation (#751) Domenic Denicola
• Re: [w3c/payment-request] Add support for merchant validation (#751) Marcos Cáceres
• Re: [w3c/payment-request] Add support for merchant validation (#751) Marcos Cáceres
• [w3c/payment-handler] Add support for communicating billing address to merchant (e.g., for VAT computation) (#314) ianbjacobs
• Re: [w3c/payment-request] Support payment method errors (#749) ianbjacobs
• Re: [w3c/payment-request] Add support for merchant validation (#751) aestes
• Re: [w3c/payment-request] Describe how to implement PaymentAddress.languageCode (#608) Rouslan Solomakhin
• Re: [w3c/payment-request] Describe how to implement PaymentAddress.languageCode (#608) Addison Phillips
• Re: [w3c/payment-request] Describe how to implement PaymentAddress.languageCode (#608) Peter Saint-Andre
• Re: [w3c/payment-request] Describe how to implement PaymentAddress.languageCode (#608) Marcos Cáceres
• Re: [w3c/payment-request] Describe how to implement PaymentAddress.languageCode (#608) Rouslan Solomakhin
• Re: [w3c/payment-request] Describe how to implement PaymentAddress.languageCode (#608) Marcos Cáceres
• Re: [w3c/payment-request] Describe how to implement PaymentAddress.languageCode (#608) Rouslan Solomakhin

Monday, 20 August 2018

• Re: [w3c/webpayments-methods-tokenization] How are empty supported* fields to be interpreted? (#48) ianbjacobs
• Re: [w3c/webpayments-methods-tokenization] How are empty supported* fields to be interpreted? (#48) ianbjacobs
• Re: [w3c/payment-handler] Need normative text for checking the origin of the SW scope against "supported_origins". (#309) ianbjacobs
• Re: [w3c/payment-handler] Incorporate the canMakePayment algorithm of the payment method good practices doc. (#313) ianbjacobs
• Re: [w3c/payment-handler] Incorporate the canMakePayment algorithm of the payment method good practices doc. (#313) Jinho Bang
• Re: [w3c/payment-request] Add ability to request billing address (#749) Marcos Cáceres
• Re: [w3c/payment-request] Add ability to request billing address (#749) Marcos Cáceres
• Re: [w3c/payment-handler] Cross-origin iframes and feature policy. (#282) Marcos Cáceres
• Re: [w3c/payment-request] Proposal to add more details to shopping cart contents and shipping option descriptions (#761) Marcos Cáceres

Saturday, 18 August 2018

• Re: [w3c/payment-request] Merchant yang ditentukan standar alamat pengiriman (#763) ianbjacobs
• Re: [w3c/payment-request] Merchant yang ditentukan standar alamat pengiriman (#762) ianbjacobs
• [w3c/payment-request] Merchant yang ditentukan standar alamat pengiriman (#763) WORLD BANK GROUP FINANCES
• [w3c/payment-request] Merchant yang ditentukan standar alamat pengiriman (#762) WORLD BANK GROUP FINANCES

Friday, 17 August 2018

• [w3c/payment-request] Proposal to add more details to shopping cart contents and shipping option descriptions (#761) Rouslan Solomakhin
• Re: [w3c/payment-handler] Incorporate the canMakePayment algorithm of the payment method good practices doc. (#313) Rouslan Solomakhin
• Re: [w3c/payment-handler] Incorporate the canMakePayment algorithm of the payment method good practices doc. (#313) ianbjacobs
• Re: [w3c/payment-handler] Incorporate the canMakePayment algorithm of the payment method good practices doc. (#313) Rouslan Solomakhin
• Re: [w3c/payment-handler] Incorporate the canMakePayment algorithm of the payment method good practices doc. (#313) Rouslan Solomakhin
• Re: [w3c/payment-handler] Incorporate the canMakePayment algorithm of the payment method good practices doc. (#313) Rouslan Solomakhin
• Re: [w3c/payment-handler] Incorporate the canMakePayment algorithm of the payment method good practices doc. (#313) Rouslan Solomakhin
• Re: [w3c/payment-handler] Incorporate the canMakePayment algorithm of the payment method good practices doc. (#313) Rouslan Solomakhin
• Re: [w3c/payment-request] Add ability to request billing address (#749) Rouslan Solomakhin
• Re: [w3c/payment-method-basic-card] add: User changes payment method section (#53) Marcos Cáceres
• Re: [w3c/payment-request] Add ability to request billing address (#749) Marcos Cáceres
• Re: [w3c/payment-request] Add ability to request billing address (#749) Marcos Cáceres
• Re: [w3c/payment-request] Add ability to request billing address (#749) Marcos Cáceres
• Re: [w3c/payment-request] Add ability to request billing address (#749) Marcos Cáceres
• Re: [w3c/payment-request] Add ability to request billing address (#749) Marcos Cáceres
• Re: [w3c/payment-request] Add ability to request billing address (#749) Marcos Cáceres

Thursday, 16 August 2018

• Re: [w3c/payment-handler] Incorporate the canMakePayment algorithm of the payment method good practices doc. (#313) ianbjacobs
• Re: [w3c/payment-request] Add ability to request billing address (#749) ianbjacobs
• Re: [w3c/payment-request] Add ability to request billing address (#749) Domenic Denicola
• [w3c/payment-handler] Incorporate the canMakePayment algorithm of the payment method good practices doc. (#313) Rouslan Solomakhin
• 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-request] Add ability to request billing address (#749) Rouslan Solomakhin
• Re: [w3c/payment-request] Add ability to request billing address (#749) Marcos Cáceres

Wednesday, 15 August 2018

• Re: [w3c/payment-request] Add ability to request billing address (#749) Rouslan Solomakhin
• Re: [w3c/payment-request] Should the PaymentRequest ID be passed to canMakePayment? (#760) Rouslan Solomakhin
• [w3c/payment-handler] Add paymentRequestID to CanMakePaymentEvent? (#312) ianbjacobs
• Re: [w3c/payment-handler] Remove modifiers from CanMakePaymentEvent? (#289) ianbjacobs
• Re: [w3c/payment-request] Should the PaymentRequest ID be passed to canMakePayment? (#760) ianbjacobs
• [w3c/payment-request] Should the PaymentRequest ID be passed to canMakePayment? (#760) rvm4
• Re: [w3c/payment-request] Modifiers and [[serializedModifierData]] not actually used anywhere. (#753) Adrian Hope-Bailie
• Re: [w3c/payment-request] Modifiers and [[serializedModifierData]] not actually used anywhere. (#753) Marcos Cáceres
• Re: [w3c/payment-request] Drop support for "Push Payments" (#759) ianbjacobs
• Re: [w3c/payment-request] Modifiers and [[serializedModifierData]] not actually used anywhere. (#753) ianbjacobs
• Re: [w3c/payment-request] Modifiers and [[serializedModifierData]] not actually used anywhere. (#753) Adrian Hope-Bailie
• Re: [w3c/webpayments-methods-tokenization] What are the supportedCryptogramTypes? (#47) Richard Waller
• Re: [w3c/payment-request] Add ability to request billing address (#749) Marcos Cáceres
• Re: [w3c/payment-request] Add ability to request billing address (#749) Marcos Cáceres
• Re: [w3c/payment-request] Add ability to request billing address (#749) Marcos Cáceres
• Re: [w3c/payment-request] Add ability to request billing address (#749) Marcos Cáceres
• Re: [w3c/payment-request] Add error reporting billing address (#750) Marcos Cáceres
• Re: [w3c/payment-request] Add error reporting billing address (#750) Marcos Cáceres
• Re: [w3c/payment-method-basic-card] add: User changes payment method section (#53) Marcos Cáceres
• Re: [w3c/payment-request] Add ability to request billing address (#749) Marcos Cáceres
• Re: [w3c/payment-request] Modifiers and [[serializedModifierData]] not actually used anywhere. (#753) Marcos Cáceres
• Re: [w3c/payment-request] Add ability to request billing address (#749) Marcos Cáceres
• Re: [w3c/payment-request] Drop support for "Push Payments" (#759) Marcos Cáceres

Tuesday, 14 August 2018

• Re: [w3c/payment-request] Modifiers and [[serializedModifierData]] not actually used anywhere. (#753) Peter Saint-Andre
• Re: [w3c/payment-request] Should API support billing address capture (for tax computation)? (#27) Rouslan Solomakhin
• Re: [w3c/payment-request] Drop support for "Push Payments" (#759) ianbjacobs
• Re: [w3c/webpayments-methods-tokenization] How are empty supported* fields to be interpreted? (#48) ianbjacobs
• Re: [w3c/payment-request] Add ability to request billing address (#749) Rouslan Solomakhin
• Re: [w3c/payment-request] Should API support billing address capture (for tax computation)? (#27) ianbjacobs
• Re: [w3c/payment-request] Should API support billing address capture (for tax computation)? (#27) Adrian Hope-Bailie
• [w3c/payment-request] Drop support for "Push Payments" (#759) Adrian Hope-Bailie
• Re: [w3c/payment-request] Modifiers and [[serializedModifierData]] not actually used anywhere. (#753) Adrian Hope-Bailie
• Re: [w3c/payment-request] Providing an `AbortSignal` instead of calling .abort() (#757) Adrian Hope-Bailie
• Re: [w3c/payment-request] Should API support billing address capture (for tax computation)? (#27) Adrian Hope-Bailie
• Re: [w3c/payment-request] Add ability to request billing address (#749) Marcos Cáceres
• Re: [w3c/payment-request] Add error reporting for payer address (#750) Marcos Cáceres
• Re: [w3c/payment-request] Add ability to request payer's address (#749) Marcos Cáceres
• Re: [w3c/payment-request] Should API support billing address capture (for tax computation)? (#27) Marcos Cáceres
• Re: [w3c/payment-request] Should API support billing address capture (for tax computation)? (#27) Marcos Cáceres

Monday, 13 August 2018

• Re: [w3c/payment-request] bless() is racy with document.body (#758) Peter Saint-Andre
• Re: [w3c/payment-request] bless() is racy with document.body (#758) Adrian Hope-Bailie
• Re: [w3c/payment-request] Should API support billing address capture (for tax computation)? (#27) Adrian Hope-Bailie
• Re: [w3c/payment-request] Add support for merchant validation (#751) Marcos Cáceres
• Re: [w3c/payment-request] Add support for merchant validation (#751) Marcos Cáceres

Saturday, 11 August 2018

• [w3c/webpayments-methods-tokenization] How are empty supported* fields to be interpreted? (#48) rvm4
• [w3c/webpayments-methods-tokenization] What are the supportedCryptogramTypes? (#47) rvm4

Friday, 10 August 2018

• Re: [w3c/payment-request] bless() is racy with document.body (#758) Marcos Cáceres
• Re: [w3c/payment-request] bless() is racy with document.body (#758) Marcos Cáceres
• Re: [w3c/payment-request] bless() is racy with document.body (#758) Domenic Denicola
• [w3c/payment-request] bless() is racy with document.body (#758) Marcos Cáceres
• Re: [w3c/payment-request] Signaling payment handler details errors (#727) Marcos Cáceres
• Re: [w3c/payment-request] Support fine-grained errors for payment methods (#752) Marcos Cáceres
• Re: [w3c/payment-request] Support fine-grained errors for payment methods (#752) Marcos Cáceres
• Re: [w3c/payment-request] fine-grained errors reporting for PaymentAddress (#712) Marcos Cáceres
• Re: [w3c/payment-request] teach retry() about payerErrors (#721) Marcos Cáceres
• Re: [w3c/payment-request] Add support for merchant validation (#751) Marcos Cáceres
• Re: [w3c/payment-request] Add error reporting for payer address (#750) Marcos Cáceres
• Re: [w3c/payment-request] Add error reporting for payer address (#750) Marcos Cáceres
• Re: [w3c/payment-request] Add error reporting for payer address (#750) Marcos Cáceres
• Re: [w3c/payment-request] Add error reporting for payer address (#750) Marcos Cáceres
• Re: [w3c/payment-request] Add ability to request payer's address (#749) Marcos Cáceres
• Re: [w3c/payment-request] Add ability to request payer's address (#749) Marcos Cáceres
• Re: [w3c/payment-request] Add error member to PaymentValidationErrors (#747) Marcos Cáceres
• Re: [w3c/payment-request] Add generic `error` member for `.retry()` (#729) Marcos Cáceres
• Re: [w3c/payment-request] Add error member to PaymentValidationErrors (#747) Marcos Cáceres
• Re: [w3c/payment-request] Add error member to PaymentValidationErrors (#747) Marcos Cáceres
• Re: [w3c/payment-request] Should API support billing address capture (for tax computation)? (#27) ianbjacobs
• Re: [w3c/payment-request] Should API support billing address capture (for tax computation)? (#27) Marcos Cáceres

Thursday, 9 August 2018

• Re: [w3c/payment-handler] Remove modifiers from CanMakePaymentEvent? (#289) ianbjacobs
• Re: [w3c/payment-handler] Removed note on payment method manifest and added reference to it (#311) ianbjacobs
• Re: [w3c/payment-handler] Removed note on payment method manifest and added reference to it (#311) Rouslan Solomakhin
• Re: [w3c/payment-request] Suggested emphasis of privacy protections (#628) searlemichael1
• Re: [w3c/payment-request] Should API support billing address capture (for tax computation)? (#27) ianbjacobs
• Re: [w3c/payment-request] Should API support billing address capture (for tax computation)? (#27) Marcos Cáceres

Wednesday, 8 August 2018

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

Tuesday, 7 August 2018

• [w3c/webpayments-methods-tokenization] Distinguish full tokenized-card from token-reference (lighter payment method) (#46) ianbjacobs
• Re: [w3c/payment-request] Add support for merchant validation (#751) Adrian Hope-Bailie

Friday, 3 August 2018

• Re: [w3c/payment-request] Should API support billing address capture (for tax computation)? (#27) ianbjacobs
• Re: [w3c/payment-handler] Normative what happens when users closing the window opened by PaymentRequestEvent.openWindow (#299) Adrian Hope-Bailie
• Re: [w3c/payment-handler] Payment Handler window `.focused` field (#307) Adrian Hope-Bailie

Thursday, 2 August 2018

• [w3c/payment-handler] Removed note on payment method manifest and added reference to it (#311) ianbjacobs
• Re: [w3c/payment-handler] Add support for PaymentValidationErrors (#306) ianbjacobs
• Re: [w3c/payment-handler] Payment Handler window `.focused` field (#307) ianbjacobs

Last message date: Friday, 31 August 2018 17:10:30 UTC