Tuesday, 31 July 2018
Monday, 30 July 2018
- Re: [w3c/payment-method-id] What can I do with a URL-based payment method identifier? (#52)
- Re: [w3c/payment-method-id] What can I do with a URL-based payment method identifier? (#52)
- Re: [w3c/payment-method-id] What can I do with a URL-based payment method identifier? (#52)
- Re: [w3c/payment-method-id] What can I do with a URL-based payment method identifier? (#52)
- Re: [w3c/payment-method-id] What can I do with a URL-based payment method identifier? (#52)
- Re: [w3c/payment-method-id] What can I do with a URL-based payment method identifier? (#52)
- Re: [w3c/payment-method-id] What can I do with a URL-based payment method identifier? (#52)
- [w3c/payment-handler] What should payees validate? (#310)
- [w3c/payment-handler] Need normative text for checking the origin of the SW scope against "supported_origins". (#309)
- [w3c/payment-handler] What mechanism allows enforcing payment handler authenticity? (#308)
- [w3c/payment-method-id] What can I do with a URL-based payment method identifier? (#52)
- Re: [w3c/payment-request] Should API support billing address capture (for tax computation)? (#27)
- Re: [w3c/payment-request] Should API support billing address capture (for tax computation)? (#27)
- Re: [w3c/payment-request] Should API support billing address capture (for tax computation)? (#27)
Thursday, 26 July 2018
- Re: [w3c/payment-request] Support fine-grained errors for payment methods (#752)
- Re: [w3c/payment-request] Should API support billing address capture (for tax computation)? (#27)
- Re: [w3c/payment-request] Support fine-grained errors for payment methods (#752)
- Re: [w3c/payment-request] Support fine-grained errors for payment methods (#752)
Wednesday, 25 July 2018
Tuesday, 24 July 2018
- Re: [w3c/payment-request] Add error member to PaymentValidationErrors (#747)
- Re: [w3c/payment-request] Add error member to PaymentValidationErrors (#747)
Monday, 23 July 2018
- Re: [w3c/3ds] User preference for strong authentication (#7)
- Re: [w3c/payment-handler] Payment Handler window `.focused` field (#307)
- Re: [w3c/payment-handler] Payment Handler window `.focused` field (#307)
- Re: [w3c/payment-handler] Payment Handler window `.focused` field (#307)
- Re: [w3c/payment-handler] Payment Handler window `.focused` field (#307)
- Re: [w3c/payment-handler] Payment Handler window `.focused` field (#307)
- Re: [w3c/payment-handler] Payment Handler window `.focused` field (#307)
- Re: [w3c/payment-handler] Payment Handler window `.focused` field (#307)
- Re: [w3c/payment-handler] Payment Handler window `.focused` field (#307)
- Re: [w3c/payment-handler] Payment Handler window `.focused` field (#307)
- Re: [w3c/payment-handler] Payment Handler window `.focused` field (#307)
- [w3c/payment-handler] Payment Handler window `.focused` field (#307)
- Re: [w3c/payment-request] Modifiers and [[serializedModifierData]] not actually used anywhere. (#753)
Thursday, 19 July 2018
- Re: [w3c/payment-request] Add ability to request payer's address (#749)
- [w3c/payment-request] Providing an `AbortSignal` instead of calling .abort() (#757)
Wednesday, 18 July 2018
- Re: [w3c/payment-request] Editorial: fix grammatical error (#756)
- Re: [w3c/payment-request] Editorial: fix grammatical error (#756)
- Re: [w3c/payment-request] Editorial: fix grammatical error (#756)
- Re: [w3c/payment-request] Fix grammatical error (#756)
- Re: [w3c/payment-request] Fix grammatical error (#756)
- [w3c/payment-request] Fix grammatical error (#756)
- Re: [w3c/payment-request] Support fine-grained errors for payment methods (#752)
- Re: [w3c/payment-request] Support fine-grained errors for payment methods (#752)
- Re: [w3c/payment-request] Support fine-grained errors for payment methods (#752)
- Re: [w3c/payment-request] Support fine-grained errors for payment methods (#752)
- Re: [w3c/payment-request] Support fine-grained errors for payment methods (#752)
Tuesday, 17 July 2018
- Re: [w3c/payment-request] Define handling of multiple applicable modifiers (#684)
- [w3c/payment-handler] Add support for PaymentValidationErrors (#306)
- Re: [w3c/webpayments-methods-tokenization] How are future card on file transactions supported through dynamic data? (#44)
Monday, 16 July 2018
- Re: [w3c/payment-request] Do we need "doc is fully active" checks on `response.complete()`? (#731)
- Re: [w3c/payment-request] Check doc fully active during response.complete() (#748)
- Re: [w3c/payment-request] Check doc fully active during response.complete() (#748)
- Re: [w3c/payment-handler] ImageObjects can now reference ImageResource (#238)
- Re: [w3c/payment-request] Add error member to PaymentValidationErrors (#747)
- Re: [w3c/payment-request] fix: state was not closed (#754)
- Re: [w3c/payment-request] fix: state was not closed (#754)
- Re: [w3c/payment-request] fix: state was not closed (#754)
- Re: [w3c/payment-request] Rename AddressErrorFields -> AddressErrors (#755)
- Re: [w3c/payment-request] Rename AddressErrorFields -> AddressErrors (#755)
- Re: [w3c/payment-request] Rename AddressErrorFields -> AddressErrors (#755)
- Re: [w3c/payment-method-basic-card] add BasicCardErrorFields (#58)
- Re: [w3c/payment-request] Rename AddressErrorFields -> AddressErrors (#755)
- [w3c/payment-request] Rename AddressErrorFields -> AddressErrors (#755)
- [w3c/payment-request] fix: state was not closed (#754)
Friday, 13 July 2018
- Re: [w3c/payment-request] Modifiers and [[serializedModifierData]] not actually used anywhere. (#753)
- Re: [w3c/payment-request] Modifiers and [[serializedModifierData]] not actually used anywhere. (#753)
- Re: [w3c/payment-request] Modifiers and [[serializedModifierData]] not actually used anywhere. (#753)
Thursday, 12 July 2018
- Re: [w3c/payment-request] Modifiers and [[serializedModifierData]] not actually used anywhere. (#753)
- Re: [w3c/payment-request] Modifiers and [[serializedModifierData]] not actually used anywhere. (#753)
- Re: [w3c/payment-request] Modifiers and [[serializedModifierData]] not actually used anywhere. (#753)
- Re: [w3c/payment-request] Modifiers and [[serializedModifierData]] not actually used anywhere. (#753)
- [w3c/payment-request] Modifiers and [[serializedMethodData]] not actually used anywhere. (#753)
Wednesday, 11 July 2018
- Re: [w3c/payment-request] Define handling of multiple applicable modifiers (#684)
- Re: [w3c/payment-request] Define handling of multiple applicable modifiers (#684)
Tuesday, 10 July 2018
- Re: [w3c/payment-request] Add generic `error` member for `.retry()` (#729)
- Re: [w3c/payment-request] Add support for merchant validation (#751)
- Re: [w3c/payment-request] Add support for merchant validation (#751)
- Re: [w3c/payment-request] Support fine-grained errors for payment methods (#752)
- Re: [w3c/payment-request] Add support for merchant validation (#751)
- Re: [w3c/payment-request] Add ability to request payer's address (#749)
- Re: [w3c/payment-request] Add ability to request payer's address (#749)
- Re: [w3c/payment-request] Add ability to request payer's address (#749)
- Re: [w3c/payment-request] Add ability to request payer's address (#749)
- Re: [w3c/payment-request] Should API support billing address capture (for tax computation)? (#27)
Monday, 9 July 2018
- Re: [w3c/payment-request] Support fine-grained errors for payment methods (#752)
- Re: [w3c/payment-request] Support fine-grained errors for payment methods (#752)
- Re: [w3c/payment-request] Support fine-grained errors for payment methods (#752)
- Re: [w3c/payment-request] Add ability to request payer's address (#749)
- Re: [w3c/payment-request] Should API support billing address capture (for tax computation)? (#27)
- Re: [w3c/payment-request] Support fine-grained errors for payment methods (#752)
- Re: [w3c/payment-request] Add ability to request payer's address (#749)
- Re: [w3c/payment-request] Add ability to request payer's address (#749)
- Re: [w3c/payment-request] Check doc fully active during response.complete() (#748)
- Re: [w3c/payment-request] Add error member to PaymentValidationErrors (#747)
- Re: [w3c/payment-request] Add [NewObject] annotations to methods (#746)
- Re: [w3c/payment-request] [NewObject] annotation (#743)
- Re: [w3c/payment-request] Add [NewObject] annotations to methods (#746)
- Re: [w3c/payment-request] Editorial: use internal slots (#726)
- Re: [w3c/payment-request] Editorial: use internal slots (#726)
- Re: [w3c/payment-request] Drop prefixes, suffixes from error field members (#745)
- Re: [w3c/payment-request] Drop `*Error` from error things ... and `payer*` (#736)
- Re: [w3c/payment-request] Drop prefixes, suffixes from error field members (#745)
- Re: [w3c/payment-request] Drop prefixes, suffixes from error field members (#745)
- Re: [w3c/payment-request] Drop prefixes, suffixes from error field members (#745)
- Re: [w3c/payment-request] Define PaymentResponse.prototype.retry() method (#720)
Friday, 6 July 2018
- Re: [w3c/payment-method-basic-card] add BasicCardErrorFields (#58)
- Re: [w3c/payment-request] Support fine-grained errors for payment methods (#752)
- [w3c/payment-method-basic-card] add BasicCardErrorFields (#58)
- Re: [w3c/payment-request] Signaling payment handler details errors (#727)
- Re: [w3c/payment-request] Signaling payment handler details errors (#727)
- [w3c/payment-request] Support fine-grained errors for payment methods (#752)
- Re: [w3c/payment-request] Add error reporting for payer address (#750)
- Re: [w3c/payment-request] Editorial: describe security mitigations #675 (#683)
- Re: [w3c/payment-request] Editorial: describe security mitigations #675 (#683)
- Re: [w3c/payment-request] Add support for merchant validation (#646)
- [w3c/payment-request] Merchantvalidation (#751)
- Re: [w3c/payment-request] Add support for merchant validation (#646)
- Re: [w3c/payment-request] Document privacy and security mitigations (#675)
- Re: [w3c/payment-request] Document privacy and security mitigations (#675)
- Re: [w3c/payment-request] Add secure origin section to security considerations (#742)
- Re: [w3c/payment-request] Add secure origin section to security considerations (#742)
- Re: [w3c/payment-request] iframe usage security subsection (#741)
- Re: [w3c/payment-request] iframe usage security subsection (#741)
- Re: [w3c/payment-request] document show() protections under security considerations (#740)
- Re: [w3c/payment-request] document show() protections under security considerations (#740)
- Re: [w3c/payment-request] Added canMakePayment() section to privacy considerations (#739)
- Re: [w3c/payment-request] Added canMakePayment() section to privacy considerations (#739)
- Re: [w3c/payment-request] Should API support billing address capture (for tax computation)? (#27)
- [w3c/payment-request] Add error reporting for payer address (#750)
- Re: [w3c/payment-request] Should API support billing address capture (for tax computation)? (#27)
- Re: [w3c/payment-request] Should API support billing address capture (for tax computation)? (#27)
- [w3c/payment-request] Add ability to request payer's address (#749)
Thursday, 5 July 2018
- [w3c/payment-request] Check doc fully active during response.complete() (#748)
- Re: [w3c/payment-request] Drop prefixes, suffixes from error field members (#745)
- [w3c/payment-request] Add error member to PaymentValidationErrors (#747)
Wednesday, 4 July 2018
- Re: [w3c/payment-request] Retrying a payment (#705)
- Re: [w3c/payment-request] Retrying a payment (#705)
Tuesday, 3 July 2018
- Re: [w3c/payment-request] [NewObject] annotation (#743)
- Re: [w3c/payment-request] Added information about redactList to privacy consideration (#738)
- Re: [w3c/payment-request] Added information about redactList to privacy consideration (#738)
- Re: [w3c/payment-request] Add [NewObject] annotations to methods (#746)
- Re: [w3c/payment-request] Add [NewObject] annotations to methods (#746)
- Re: [w3c/payment-request] EventTarget is used by never linked to (#744)
- [w3c/payment-request] Add [NewObject] annotations to methods (#746)
- Re: [w3c/payment-request] Drop prefixes, suffixes from error field members (#745)
- [w3c/payment-request] Drop prefixes, suffixes from error field members (#745)
- Re: [w3c/payment-request] Add PaymentResponse.prototype.onpayerdetailchange (#724)
- Re: [w3c/payment-request] Add PaymentResponse.prototype.onpayerdetailchange (#724)
- Re: [w3c/payment-request] Add PaymentResponse.prototype.onpayerdetailchange (#724)