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

Christian Liebel

• Re: [w3c/payment-request] Editorial: fix grammatical error (#756) (Wednesday, 18 July)
• [w3c/payment-request] Fix grammatical error (#756) (Wednesday, 18 July)

Domenic Denicola

• Re: [w3c/payment-request] fix: state was not closed (#754) (Monday, 16 July)
• Re: [w3c/payment-request] Rename AddressErrorFields -> AddressErrors (#755) (Monday, 16 July)
• Re: [w3c/payment-request] Modifiers and [[serializedModifierData]] not actually used anywhere. (#753) (Thursday, 12 July)
• Re: [w3c/payment-request] Add ability to request payer's address (#749) (Monday, 9 July)
• Re: [w3c/payment-request] Should API support billing address capture (for tax computation)? (#27) (Monday, 9 July)
• Re: [w3c/payment-request] Support fine-grained errors for payment methods (#752) (Monday, 9 July)
• Re: [w3c/payment-request] Add ability to request payer's address (#749) (Monday, 9 July)
• Re: [w3c/payment-request] Add ability to request payer's address (#749) (Monday, 9 July)
• Re: [w3c/payment-request] Check doc fully active during response.complete() (#748) (Monday, 9 July)
• Re: [w3c/payment-request] Add error member to PaymentValidationErrors (#747) (Monday, 9 July)
• Re: [w3c/payment-request] Add [NewObject] annotations to methods (#746) (Monday, 9 July)
• Re: [w3c/payment-request] [NewObject] annotation (#743) (Monday, 9 July)
• Re: [w3c/payment-request] Add [NewObject] annotations to methods (#746) (Monday, 9 July)
• Re: [w3c/payment-request] Drop prefixes, suffixes from error field members (#745) (Monday, 9 July)

ianbjacobs

• [w3c/webpayments-methods-tokenization] Should there be an option to provide key (instead of keyProviderURL)? (#45) (Tuesday, 31 July)
• Re: [w3c/payment-method-id] What can I do with a URL-based payment method identifier? (#52) (Monday, 30 July)
• Re: [w3c/payment-method-id] What can I do with a URL-based payment method identifier? (#52) (Monday, 30 July)
• Re: [w3c/payment-method-id] What can I do with a URL-based payment method identifier? (#52) (Monday, 30 July)
• Re: [w3c/payment-request] Should API support billing address capture (for tax computation)? (#27) (Monday, 30 July)
• Re: [w3c/payment-request] Should API support billing address capture (for tax computation)? (#27) (Monday, 30 July)
• Re: [w3c/payment-handler] Payment Handler window `.focused` field (#307) (Monday, 23 July)
• Re: [w3c/payment-handler] Payment Handler window `.focused` field (#307) (Monday, 23 July)
• Re: [w3c/payment-handler] Payment Handler window `.focused` field (#307) (Monday, 23 July)
• Re: [w3c/payment-handler] Payment Handler window `.focused` field (#307) (Monday, 23 July)
• Re: [w3c/payment-handler] Payment Handler window `.focused` field (#307) (Monday, 23 July)
• Re: [w3c/payment-request] Define handling of multiple applicable modifiers (#684) (Tuesday, 17 July)
• [w3c/payment-handler] Add support for PaymentValidationErrors (#306) (Tuesday, 17 July)
• Re: [w3c/webpayments-methods-tokenization] How are future card on file transactions supported through dynamic data? (#44) (Tuesday, 17 July)

L. David Baron

• Re: [w3c/payment-handler] ImageObjects can now reference ImageResource (#238) (Monday, 16 July)

Marcos Cáceres

• Re: [w3c/payment-request] Support fine-grained errors for payment methods (#752) (Thursday, 26 July)
• Re: [w3c/payment-request] Support fine-grained errors for payment methods (#752) (Thursday, 26 July)
• Re: [w3c/payment-request] Add error member to PaymentValidationErrors (#747) (Tuesday, 24 July)
• Re: [w3c/payment-request] Add error member to PaymentValidationErrors (#747) (Tuesday, 24 July)
• Re: [w3c/payment-request] Add ability to request payer's address (#749) (Thursday, 19 July)
• [w3c/payment-request] Providing an `AbortSignal` instead of calling .abort() (#757) (Thursday, 19 July)
• Re: [w3c/payment-request] Editorial: fix grammatical error (#756) (Wednesday, 18 July)
• Re: [w3c/payment-request] Editorial: fix grammatical error (#756) (Wednesday, 18 July)
• Re: [w3c/payment-request] Fix grammatical error (#756) (Wednesday, 18 July)
• Re: [w3c/payment-request] Fix grammatical error (#756) (Wednesday, 18 July)
• Re: [w3c/payment-request] Support fine-grained errors for payment methods (#752) (Wednesday, 18 July)
• Re: [w3c/payment-request] Do we need "doc is fully active" checks on `response.complete()`? (#731) (Monday, 16 July)
• Re: [w3c/payment-request] Check doc fully active during response.complete() (#748) (Monday, 16 July)
• Re: [w3c/payment-request] Check doc fully active during response.complete() (#748) (Monday, 16 July)
• Re: [w3c/payment-request] Add error member to PaymentValidationErrors (#747) (Monday, 16 July)
• Re: [w3c/payment-request] fix: state was not closed (#754) (Monday, 16 July)
• Re: [w3c/payment-request] fix: state was not closed (#754) (Monday, 16 July)
• Re: [w3c/payment-request] Rename AddressErrorFields -> AddressErrors (#755) (Monday, 16 July)
• Re: [w3c/payment-request] Rename AddressErrorFields -> AddressErrors (#755) (Monday, 16 July)
• Re: [w3c/payment-method-basic-card] add BasicCardErrorFields (#58) (Monday, 16 July)
• Re: [w3c/payment-request] Rename AddressErrorFields -> AddressErrors (#755) (Monday, 16 July)
• [w3c/payment-request] Rename AddressErrorFields -> AddressErrors (#755) (Monday, 16 July)
• [w3c/payment-request] fix: state was not closed (#754) (Monday, 16 July)
• Re: [w3c/payment-request] Modifiers and [[serializedModifierData]] not actually used anywhere. (#753) (Friday, 13 July)
• Re: [w3c/payment-request] Modifiers and [[serializedModifierData]] not actually used anywhere. (#753) (Friday, 13 July)
• Re: [w3c/payment-request] Modifiers and [[serializedModifierData]] not actually used anywhere. (#753) (Thursday, 12 July)
• Re: [w3c/payment-request] Modifiers and [[serializedModifierData]] not actually used anywhere. (#753) (Thursday, 12 July)
• Re: [w3c/payment-request] Modifiers and [[serializedModifierData]] not actually used anywhere. (#753) (Thursday, 12 July)
• [w3c/payment-request] Modifiers and [[serializedMethodData]] not actually used anywhere. (#753) (Thursday, 12 July)
• Re: [w3c/payment-request] Define handling of multiple applicable modifiers (#684) (Wednesday, 11 July)
• Re: [w3c/payment-request] Add generic `error` member for `.retry()` (#729) (Tuesday, 10 July)
• Re: [w3c/payment-request] Add support for merchant validation (#751) (Tuesday, 10 July)
• Re: [w3c/payment-request] Add support for merchant validation (#751) (Tuesday, 10 July)
• Re: [w3c/payment-request] Support fine-grained errors for payment methods (#752) (Tuesday, 10 July)
• Re: [w3c/payment-request] Add support for merchant validation (#751) (Tuesday, 10 July)
• Re: [w3c/payment-request] Add ability to request payer's address (#749) (Tuesday, 10 July)
• Re: [w3c/payment-request] Add ability to request payer's address (#749) (Tuesday, 10 July)
• Re: [w3c/payment-request] Add ability to request payer's address (#749) (Tuesday, 10 July)
• Re: [w3c/payment-request] Add ability to request payer's address (#749) (Tuesday, 10 July)
• Re: [w3c/payment-request] Should API support billing address capture (for tax computation)? (#27) (Tuesday, 10 July)
• Re: [w3c/payment-request] Support fine-grained errors for payment methods (#752) (Monday, 9 July)
• Re: [w3c/payment-request] Support fine-grained errors for payment methods (#752) (Monday, 9 July)
• Re: [w3c/payment-request] Support fine-grained errors for payment methods (#752) (Monday, 9 July)
• Re: [w3c/payment-request] Editorial: use internal slots (#726) (Monday, 9 July)
• Re: [w3c/payment-request] Editorial: use internal slots (#726) (Monday, 9 July)
• Re: [w3c/payment-request] Drop prefixes, suffixes from error field members (#745) (Monday, 9 July)
• Re: [w3c/payment-request] Drop `*Error` from error things ... and `payer*` (#736) (Monday, 9 July)
• Re: [w3c/payment-request] Drop prefixes, suffixes from error field members (#745) (Monday, 9 July)
• Re: [w3c/payment-request] Drop prefixes, suffixes from error field members (#745) (Monday, 9 July)
• Re: [w3c/payment-request] Define PaymentResponse.prototype.retry() method (#720) (Monday, 9 July)
• Re: [w3c/payment-method-basic-card] add BasicCardErrorFields (#58) (Friday, 6 July)
• Re: [w3c/payment-request] Support fine-grained errors for payment methods (#752) (Friday, 6 July)
• [w3c/payment-method-basic-card] add BasicCardErrorFields (#58) (Friday, 6 July)
• Re: [w3c/payment-request] Signaling payment handler details errors (#727) (Friday, 6 July)
• Re: [w3c/payment-request] Signaling payment handler details errors (#727) (Friday, 6 July)
• [w3c/payment-request] Support fine-grained errors for payment methods (#752) (Friday, 6 July)
• Re: [w3c/payment-request] Add error reporting for payer address (#750) (Friday, 6 July)
• Re: [w3c/payment-request] Editorial: describe security mitigations #675 (#683) (Friday, 6 July)
• Re: [w3c/payment-request] Editorial: describe security mitigations #675 (#683) (Friday, 6 July)
• Re: [w3c/payment-request] Add support for merchant validation (#646) (Friday, 6 July)
• [w3c/payment-request] Merchantvalidation (#751) (Friday, 6 July)
• Re: [w3c/payment-request] Add support for merchant validation (#646) (Friday, 6 July)
• Re: [w3c/payment-request] Document privacy and security mitigations (#675) (Friday, 6 July)
• Re: [w3c/payment-request] Document privacy and security mitigations (#675) (Friday, 6 July)
• Re: [w3c/payment-request] Add secure origin section to security considerations (#742) (Friday, 6 July)
• Re: [w3c/payment-request] Add secure origin section to security considerations (#742) (Friday, 6 July)
• Re: [w3c/payment-request] iframe usage security subsection (#741) (Friday, 6 July)
• Re: [w3c/payment-request] iframe usage security subsection (#741) (Friday, 6 July)
• Re: [w3c/payment-request] document show() protections under security considerations (#740) (Friday, 6 July)
• Re: [w3c/payment-request] document show() protections under security considerations (#740) (Friday, 6 July)
• Re: [w3c/payment-request] Added canMakePayment() section to privacy considerations (#739) (Friday, 6 July)
• Re: [w3c/payment-request] Added canMakePayment() section to privacy considerations (#739) (Friday, 6 July)
• Re: [w3c/payment-request] Should API support billing address capture (for tax computation)? (#27) (Friday, 6 July)
• [w3c/payment-request] Add error reporting for payer address (#750) (Friday, 6 July)
• Re: [w3c/payment-request] Should API support billing address capture (for tax computation)? (#27) (Friday, 6 July)
• Re: [w3c/payment-request] Should API support billing address capture (for tax computation)? (#27) (Friday, 6 July)
• [w3c/payment-request] Add ability to request payer's address (#749) (Friday, 6 July)
• [w3c/payment-request] Check doc fully active during response.complete() (#748) (Thursday, 5 July)
• Re: [w3c/payment-request] Drop prefixes, suffixes from error field members (#745) (Thursday, 5 July)
• [w3c/payment-request] Add error member to PaymentValidationErrors (#747) (Thursday, 5 July)
• Re: [w3c/payment-request] Retrying a payment (#705) (Wednesday, 4 July)
• Re: [w3c/payment-request] Retrying a payment (#705) (Wednesday, 4 July)
• Re: [w3c/payment-request] [NewObject] annotation (#743) (Tuesday, 3 July)
• Re: [w3c/payment-request] Added information about redactList to privacy consideration (#738) (Tuesday, 3 July)
• Re: [w3c/payment-request] Added information about redactList to privacy consideration (#738) (Tuesday, 3 July)
• Re: [w3c/payment-request] Add [NewObject] annotations to methods (#746) (Tuesday, 3 July)
• Re: [w3c/payment-request] Add [NewObject] annotations to methods (#746) (Tuesday, 3 July)
• Re: [w3c/payment-request] EventTarget is used by never linked to (#744) (Tuesday, 3 July)
• [w3c/payment-request] Add [NewObject] annotations to methods (#746) (Tuesday, 3 July)
• Re: [w3c/payment-request] Drop prefixes, suffixes from error field members (#745) (Tuesday, 3 July)
• [w3c/payment-request] Drop prefixes, suffixes from error field members (#745) (Tuesday, 3 July)
• Re: [w3c/payment-request] Add PaymentResponse.prototype.onpayerdetailchange (#724) (Tuesday, 3 July)
• Re: [w3c/payment-request] Add PaymentResponse.prototype.onpayerdetailchange (#724) (Tuesday, 3 July)
• Re: [w3c/payment-request] Add PaymentResponse.prototype.onpayerdetailchange (#724) (Tuesday, 3 July)
• Re: [w3c/payment-request] add paymentmethodchange event (#695) (Monday, 2 July)

Peter Saint-Andre

• Re: [w3c/payment-method-id] What can I do with a URL-based payment method identifier? (#52) (Monday, 30 July)
• Re: [w3c/payment-method-id] What can I do with a URL-based payment method identifier? (#52) (Monday, 30 July)
• Re: [w3c/3ds] User preference for strong authentication (#7) (Monday, 23 July)
• Re: [w3c/payment-request] Support fine-grained errors for payment methods (#752) (Wednesday, 18 July)
• Re: [w3c/payment-request] Modifiers and [[serializedModifierData]] not actually used anywhere. (#753) (Friday, 13 July)
• Re: [w3c/payment-request] Define handling of multiple applicable modifiers (#684) (Wednesday, 11 July)

Rouslan Solomakhin

• Re: [w3c/payment-method-id] What can I do with a URL-based payment method identifier? (#52) (Monday, 30 July)
• Re: [w3c/payment-method-id] What can I do with a URL-based payment method identifier? (#52) (Monday, 30 July)
• [w3c/payment-handler] What should payees validate? (#310) (Monday, 30 July)
• [w3c/payment-handler] Need normative text for checking the origin of the SW scope against "supported_origins". (#309) (Monday, 30 July)
• [w3c/payment-handler] What mechanism allows enforcing payment handler authenticity? (#308) (Monday, 30 July)
• [w3c/payment-method-id] What can I do with a URL-based payment method identifier? (#52) (Monday, 30 July)
• Re: [w3c/payment-request] Should API support billing address capture (for tax computation)? (#27) (Monday, 30 July)
• Re: [w3c/payment-request] Should API support billing address capture (for tax computation)? (#27) (Thursday, 26 July)
• Re: [w3c/payment-request] Support fine-grained errors for payment methods (#752) (Thursday, 26 July)
• Re: [w3c/payment-request] Add error member to PaymentValidationErrors (#747) (Wednesday, 25 July)
• Re: [w3c/payment-handler] Payment Handler window `.focused` field (#307) (Monday, 23 July)
• Re: [w3c/payment-handler] Payment Handler window `.focused` field (#307) (Monday, 23 July)
• Re: [w3c/payment-handler] Payment Handler window `.focused` field (#307) (Monday, 23 July)
• Re: [w3c/payment-handler] Payment Handler window `.focused` field (#307) (Monday, 23 July)
• Re: [w3c/payment-handler] Payment Handler window `.focused` field (#307) (Monday, 23 July)
• [w3c/payment-handler] Payment Handler window `.focused` field (#307) (Monday, 23 July)
• Re: [w3c/payment-request] Modifiers and [[serializedModifierData]] not actually used anywhere. (#753) (Monday, 23 July)
• Re: [w3c/payment-request] Support fine-grained errors for payment methods (#752) (Wednesday, 18 July)
• Re: [w3c/payment-request] Support fine-grained errors for payment methods (#752) (Wednesday, 18 July)
• Re: [w3c/payment-request] Support fine-grained errors for payment methods (#752) (Wednesday, 18 July)

Last message date: Tuesday, 31 July 2018 12:31:44 UTC