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

Saturday, 30 June 2018

• Re: [w3c/payment-request] Signaling payment handler details errors (#727) Marcos Cáceres
• Re: [w3c/payment-request] Signaling payment handler details errors (#727) Marcos Cáceres
• [w3c/payment-method-basic-card] Signaling payment handler details errors (#57) Marcos Cáceres

Thursday, 28 June 2018

• [w3c/payment-request] EventTarget is used by never linked to (#744) Marcos Cáceres
• [w3c/payment-request] [NewObject] annotation (#743) Marcos Cáceres
• Re: [w3c/payment-request] Define PaymentResponse.prototype.retry() method (#720) Marcos Cáceres
• Re: [w3c/payment-request] Add PaymentResponse.prototype.onpayerdetailchange (#724) Marcos Cáceres
• Re: [w3c/payment-request] Add PaymentResponse.prototype.onpayerdetailchange (#724) Marcos Cáceres
• Re: [w3c/payment-request] Add PaymentResponse.prototype.onpayerdetailchange (#724) Marcos Cáceres
• Re: [w3c/payment-request] Add PaymentResponse.prototype.onpayerdetailchange (#724) Domenic Denicola
• Re: [w3c/payment-request] Add PaymentResponse.prototype.onpayerdetailchange (#724) Marcos Cáceres
• Re: [w3c/payment-request] Add PaymentResponse.prototype.onpayerdetailchange (#724) Marcos Cáceres
• Re: [w3c/payment-request] Added information about redactList to privacy consideration (#738) ianbjacobs
• Re: [w3c/payment-request] Added information about redactList to privacy consideration (#738) ianbjacobs
• Re: [w3c/payment-request] Added information about redactList to privacy consideration (#738) Marcos Cáceres
• Re: [w3c/payment-request] Signaling payment handler details errors (#727) Marcos Cáceres

Wednesday, 27 June 2018

• Re: [w3c/payment-request] Response timeout could leave page/user in confused state. (#737) Adrian Hope-Bailie
• [w3c/3ds] User preference for strong authentication (#7) ianbjacobs

Tuesday, 26 June 2018

• [w3c/payment-request] Add secure origin section to security considerations (#742) ianbjacobs
• [w3c/payment-request] iframe usage security subsection (#741) ianbjacobs
• [w3c/payment-request] document show() protections under security considerations (#740) ianbjacobs
• [w3c/payment-request] Added canMakePayment() section to privacy considerations (#739) ianbjacobs
• [w3c/payment-request] Added information about redactList to privacy consideration (#738) ianbjacobs
• Re: [w3c/payment-request] Add PaymentResponse.prototype.onpayerdetailchange (#724) Marcos Cáceres
• Re: [w3c/payment-request] Add PaymentResponse.prototype.onpayerdetailchange (#724) Domenic Denicola
• Re: [w3c/payment-request] Signaling payment handler details errors (#727) Marcos Cáceres
• Re: [w3c/payment-request] Retry request abort the update (#723) Marcos Cáceres
• Re: [w3c/payment-request] Retry request abort the update (#723) Marcos Cáceres
• Re: [w3c/payment-request] Response timeout could leave page/user in confused state. (#737) Marcos Cáceres
• Re: [w3c/payment-request] Response timeout could leave page/user in confused state. (#737) ianbjacobs
• Re: [w3c/payment-request] Response timeout could leave page/user in confused state. (#737) Marcos Cáceres
• [w3c/payment-request] Response timeout could leave page/user in confused state. (#737) Marcos Cáceres
• Re: [w3c/payment-request] Retry request abort the update (#723) Marcos Cáceres
• Re: [w3c/payment-request] Retry request abort the update (#723) Domenic Denicola
• Re: [w3c/webpayments-methods-tokenization] How are future card on file transactions supported through dynamic data? (#44) ianbjacobs

Monday, 25 June 2018

• Re: [w3c/payment-request] Add PaymentResponse.onpayerdetailchange (#724) Marcos Cáceres
• Re: [w3c/payment-request] Retry request abort the update (#723) Marcos Cáceres
• Re: [w3c/payment-request] Retry request abort the update (#723) Marcos Cáceres
• Re: [w3c/payment-request] Retry request abort the update (#723) Marcos Cáceres
• Re: [w3c/payment-request] Retry request abort the update (#723) Marcos Cáceres
• Re: [w3c/payment-request] Retry request abort the update (#723) Marcos Cáceres
• Re: [w3c/payment-request] Retry request abort the update (#723) Marcos Cáceres
• Re: [w3c/payment-request] fix: complete() returns rejected promise (#732) Marcos Cáceres
• Re: [w3c/payment-request] fix: complete() returns rejected promise (#732) Marcos Cáceres
• Re: [w3c/payment-request] fix: complete() returns rejected promise (#732) Marcos Cáceres
• Re: [w3c/payment-request] Retry request abort the update (#723) Marcos Cáceres
• Re: [w3c/payment-request] Retry request abort the update (#723) Domenic Denicola
• Re: [w3c/payment-request] fix: complete() returns rejected promise (#732) Marcos Cáceres
• Re: [w3c/payment-request] Drop `*Error` from error things (#736) Marcos Cáceres
• Re: [w3c/payment-request] Retry request abort the update (#723) Marcos Cáceres
• Re: [w3c/payment-request] Drop `*Error` from error things (#736) Domenic Denicola
• Re: [w3c/payment-request] teach retry() about payerErrors (#721) Marcos Cáceres
• Re: [w3c/payment-request] teach retry() about payerErrors (#721) Marcos Cáceres
• [w3c/payment-request] Drop `*Error` from error things (#736) Marcos Cáceres
• Re: [w3c/payment-request] teach retry() about payerErrors (#721) Marcos Cáceres
• Re: [w3c/payment-request] teach retry() about payerErrors (#721) Domenic Denicola
• Re: [w3c/payment-request] Add PaymentResponse.onpayerdetailchange (#724) Wanli Yang
• Re: [w3c/payment-request] teach retry() about payerErrors (#721) Marcos Cáceres
• Re: [w3c/payment-request] Do we need "doc is fully active" checks on `response.complete()`? (#731) Domenic Denicola
• Re: [w3c/payment-request] teach retry() about payerErrors (#721) Domenic Denicola
• Re: [w3c/payment-request] Editorial: complete() returns rejected promise (#732) Domenic Denicola
• Re: [w3c/payment-request] teach retry() about payerErrors (#721) Marcos Cáceres
• Re: [w3c/payment-request] Add PaymentResponse.onpayerdetailchange (#724) Marcos Cáceres
• Re: [w3c/payment-request] Add PaymentResponse.onpayerdetailchange (#724) ianbjacobs

Friday, 22 June 2018

• Re: [w3c/payment-request] Follow up on APA Comments on Web Payments FPWDs (#735) Marcos Cáceres
• Re: [w3c/payment-request] Follow up on APA Comments on Web Payments FPWDs (#735) ianbjacobs
• [w3c/payment-request] Follow up on APA Comments on Web Payments FPWDs (#735) Marcos Cáceres
• Re: [w3c/payment-request] payment modifier brings error (#637) dtanphat9388

Thursday, 21 June 2018

• Re: [w3c/payment-request] editorial: add retry() to state diagram (#734) Marcos Cáceres
• Re: [w3c/payment-request] Update state diagram to include retry() (#728) Marcos Cáceres
• Re: [w3c/payment-request] Define PaymentResponse.prototype.retry() method (#720) Marcos Cáceres
• Re: [w3c/payment-request] add paymentmethodchange event (#695) Marcos Cáceres
• Re: [w3c/payment-request] Add equivalent of applepaypaymentmethodchanged (#662) Marcos Cáceres
• Re: [w3c/payment-request] add paymentmethodchange event (#695) Marcos Cáceres
• [w3c/payment-handler] Simplifying functional event handling (#305) Jake Archibald
• Re: [w3c/payment-request] editorial: add retry() to state diagram (#734) ianbjacobs
• Re: [w3c/payment-request] editorial: add retry() to state diagram (#734) Marcos Cáceres
• Re: [w3c/payment-request] editorial: add retry() to state diagram (#734) ianbjacobs

Wednesday, 20 June 2018

• Re: [w3c/payment-request] editorial: add retry() state (#734) Marcos Cáceres
• [w3c/payment-request] editorial: add retry() state (#734) Marcos Cáceres
• Re: [w3c/payment-request] Fix a small bug in `abort`'s error handling. (#733) Marcos Cáceres
• Re: [w3c/payment-request] Fix a small bug in `abort`'s error handling. (#733) Marcos Cáceres
• Re: [w3c/payment-request] Fix a small bug in `abort`'s error handling. (#733) Marcos Cáceres
• Re: [w3c/payment-request] Fix a small bug in `abort`'s error handling. (#733) Marcos Cáceres
• [w3c/payment-request] Fix a small bug in `abort`'s error handling. (#733) Blake Kaplan

Tuesday, 19 June 2018

• Re: [w3c/payment-request] Define PaymentResponse.prototype.retry() method (#720) Marcos Cáceres
• Re: [w3c/payment-request] Define PaymentResponse.prototype.retry() method (#720) Marcos Cáceres
• Re: [w3c/payment-request] Do we need "doc is fully active" checks on `response.complete()`? (#731) Marcos Cáceres
• [w3c/payment-request] Editorial: complete() returns rejected promise (#732) Marcos Cáceres
• Re: [w3c/payment-request] Define PaymentResponse.prototype.retry() method (#720) Marcos Cáceres
• [w3c/payment-request] Do we need "doc is fully active" checks on `response.complete()`? (#731) Marcos Cáceres

Monday, 18 June 2018

• Re: [w3c/payment-request] Define PaymentResponse.prototype.retry() method (#720) Marcos Cáceres
• Re: [w3c/payment-request] Define PaymentResponse.prototype.retry() method (#720) Marcos Cáceres
• [w3c/webpayments-methods-tokenization] How are future card on file transactions supported through dynamic data? (#44) ianbjacobs
• Re: [w3c/payment-request] Add PaymentResponse.onpayerdetailchange (#724) DannyRussellWP

Thursday, 14 June 2018

• Re: [w3c/webpayments-methods-tokenization] Token properties? (#25) ianbjacobs
• Re: [w3c/webpayments-methods-tokenization] Token properties? (#25) ianbjacobs
• Re: [w3c/webpayments-methods-tokenization] Linkage to BasicCard Spec (#17) ianbjacobs
• Re: [w3c/webpayments-methods-tokenization] Linkage to BasicCard Spec (#17) ianbjacobs
• Re: [w3c/webpayments-methods-tokenization] Is billing address required? (#40) ianbjacobs
• Re: [w3c/webpayments-methods-tokenization] Is billing address required? (#40) ianbjacobs
• Re: [w3c/webpayments-methods-tokenization] Add PAR to response data? (#38) ianbjacobs
• Re: [w3c/webpayments-methods-tokenization] Add PAR to response data? (#38) ianbjacobs
• Re: [w3c/webpayments-methods-tokenization] Add PAR to response data? (#38) ianbjacobs
• Re: [w3c/webpayments-methods-tokenization] Is cardholderName required? (#42) ianbjacobs
• Re: [w3c/webpayments-methods-tokenization] Is cardholderName required? (#42) ianbjacobs
• Re: [w3c/payment-request] Always requiring CVV? (#730) Marcos Cáceres
• Re: [w3c/payment-request] Always requiring CVV? (#730) Marcos Cáceres
• Re: [w3c/payment-request] Add PaymentResponse.onpayerdetailchange (#724) Marcos Cáceres
• Re: [w3c/payment-request] Add PaymentResponse.onpayerdetailchange (#724) Marcos Cáceres
• Re: [w3c/payment-request] Add PaymentResponse.onpayerdetailchange (#724) ianbjacobs
• Re: [w3c/payment-request] Add PaymentResponse.onpayerdetailchange (#724) Marcos Cáceres
• Re: [w3c/payment-request] Add PaymentResponse.onpayerdetailchange (#724) Peter Saint-Andre
• Re: [w3c/payment-request] Add PaymentResponse.onpayerdetailchange (#724) Marcos Cáceres
• Re: [w3c/payment-request] Add PaymentResponse.onpayerdetailchange (#724) Peter Saint-Andre
• Re: [w3c/payment-request] Add PaymentResponse.onpayerdetailchange (#724) Marcos Cáceres
• Re: [w3c/payment-request] Add PaymentResponse.onpayerdetailchange (#724) Marcos Cáceres
• Re: [w3c/payment-request] Add PaymentResponse.onpayerdetailchange (#724) ianbjacobs
• Re: [w3c/payment-request] Always requiring CVV? (#730) ianbjacobs
• Re: [w3c/payment-request] Always requiring CVV? (#730) Marcos Cáceres
• [w3c/payment-request] Always requiring CVV? (#730) Marcos Cáceres
• [w3c/payment-request] Add generic `error` member for `.retry()` (#729) Marcos Cáceres
• Re: [w3c/payment-request] Retrying a payment (#705) ianbjacobs
• [w3c/payment-request] Update state diagram to include retry() (#728) ianbjacobs
• Re: [w3c/payment-request] Signaling payment handler details errors (#727) ianbjacobs
• Re: [w3c/payment-request] Signaling payment handler details errors (#727) Marcos Cáceres
• Re: [w3c/payment-request] Signaling payment handler details errors (#727) ianbjacobs
• Re: [w3c/payment-request] Signaling payment handler details errors (#727) Marcos Cáceres
• Re: [w3c/payment-request] Signaling payment handler details errors (#727) ianbjacobs
• Re: [w3c/payment-request] Should API support billing address capture (for tax computation)? (#27) tricky456
• Re: [w3c/payment-request] Should API support billing address capture (for tax computation)? (#27) Marcos Cáceres
• [w3c/payment-request] Signaling payment handler details errors (#727) Marcos Cáceres

Wednesday, 13 June 2018

• Re: [w3c/3ds] Change `requestLevel` in response to sheet data changes (#6) ianbjacobs
• Re: [w3c/3ds] Change `requestLevel` in response to sheet data changes (#6) ianbjacobs

Tuesday, 12 June 2018

• Re: [w3c/payment-request] define PaymentResponse.retry() method (#720) Marcos Cáceres
• Re: [w3c/payment-request] define PaymentResponse.retry() method (#720) Marcos Cáceres
• Re: [w3c/payment-request] add paymentmethodchange event (#695) Marcos Cáceres
• Re: [w3c/webpayments-methods-tokenization] How/whether to handle token sharing use cases (#41) ianbjacobs
• Re: [w3c/payment-request] define PaymentResponse.retry() method (#720) Domenic Denicola
• Re: [w3c/payment-request] add paymentmethodchange event (#695) Domenic Denicola
• Re: [w3c/payment-request] Should API support billing address capture (for tax computation)? (#27) Krystian Czesak
• 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
• Re: [w3c/payment-request] Should API support billing address capture (for tax computation)? (#27) ianbjacobs
• Re: [w3c/payment-request] define PaymentResponse.retry() method (#720) Marcos Cáceres
• Re: [w3c/payment-request] define PaymentResponse.retry() method (#720) Marcos Cáceres
• Re: [w3c/payment-request] define PaymentResponse.retry() method (#720) Marcos Cáceres
• Re: [w3c/payment-request] define PaymentResponse.retry() method (#720) Marcos Cáceres
• Re: [w3c/payment-request] define PaymentResponse.retry() method (#720) ianbjacobs
• Re: [w3c/payment-request] define PaymentResponse.retry() method (#720) Marcos Cáceres
• Re: [w3c/payment-request] Add explicit extension point to matching algo (#470) Marcos Cáceres
• Re: [w3c/payment-request] Add explicit extension point to matching algo (#470) Marcos Cáceres
• Re: [w3c/payment-request] Should API support billing address capture (for tax computation)? (#27) Marcos Cáceres
• [w3c/payment-request] Editorial: use internal slots (#726) Marcos Cáceres
• Re: [w3c/payment-request] Update test-plan.md after web-platform-tests repo move (#725) Marcos Cáceres
• Re: [w3c/payment-request] Update test-plan.md after web-platform-tests repo move (#725) Marcos Cáceres
• [w3c/payment-request] Update test-plan.md after web-platform-tests repo move (#725) Philip Jägenstedt
• Re: [w3c/payment-request] define PaymentResponse.retry() method (#720) Marcos Cáceres
• Re: [w3c/payment-request] add paymentmethodchange event (#695) Marcos Cáceres
• [w3c/payment-request] Add PaymentResponse.onpayerdetailchange (#724) Marcos Cáceres
• [w3c/payment-request] Retry request abort the update (#723) Marcos Cáceres

Saturday, 9 June 2018

• Re: [w3c/payment-request] chore(PULL_REQUEST_TEMPLATE.md): note impact on payment handler (#722) Kronik-Lilus
• [w3c/payment-request] chore(PULL_REQUEST_TEMPLATE.md): note impact on payment handler (#722) Kronik-Lilus

Thursday, 7 June 2018

• Re: [w3c/payment-request] teach retry() about payerErrors (#721) Marcos Cáceres
• Re: [w3c/payment-request] teach retry() about payerErrors (#721) Marcos Cáceres
• Re: [w3c/payment-request] teach retry() about payerErrors (#721) Marcos Cáceres
• [w3c/payment-request] teach retry() about payerErrors (#721) Marcos Cáceres
• Re: [w3c/payment-request] define PaymentResponse.retry() method (#720) Marcos Cáceres
• Re: [w3c/payment-request] define PaymentResponse.retry() method (#720) Marcos Cáceres
• [w3c/payment-request] define PaymentResponse.retry() method (#720) Marcos Cáceres

Wednesday, 6 June 2018

• [w3c/3ds] Change `requestLevel` in response to sheet data changes (#6) Adam Solove
• Re: [w3c/payment-request] fine-grained errors reporting for PaymentAddress (#712) ianbjacobs
• Re: [w3c/payment-request] Define PaymentResponse.retry() method (#715) Marcos Cáceres
• Re: [w3c/payment-request] Teach retry() about payerErrors (#716) Marcos Cáceres
• Re: [w3c/payment-request] Define PaymentResponse.retry() method (#715) Marcos Cáceres
• Re: [w3c/payment-request] add paymentmethodchange event (#695) Marcos Cáceres
• Re: [w3c/payment-request] add paymentmethodchange event (#695) Marcos Cáceres
• Re: [w3c/payment-request] add paymentmethodchange event (#695) Domenic Denicola
• Re: [w3c/payment-request] add paymentmethodchange event (#695) Marcos Cáceres
• Re: [w3c/payment-request] fine-grained errors reporting for PaymentAddress (#712) Marcos Cáceres
• Re: [w3c/payment-request] Fine grained error recovery for fields (#647) Marcos Cáceres
• Re: [w3c/payment-request] fine-grained errors reporting for PaymentAddress (#712) Marcos Cáceres
• Re: [w3c/payment-request] fine-grained errors reporting for PaymentAddress (#712) Marcos Cáceres
• Re: [w3c/payment-request] fine-grained errors reporting for PaymentAddress (#712) Marcos Cáceres

Tuesday, 5 June 2018

• Re: [w3c/payment-request] add paymentmethodchange event (#695) Domenic Denicola
• Re: [w3c/payment-request] fine-grained errors reporting for PaymentAddress (#712) Domenic Denicola
• Re: [w3c/payment-request] add paymentmethodchange event (#695) Marcos Cáceres
• Re: [w3c/payment-request] add paymentmethodchange event (#695) Marcos Cáceres
• Re: [w3c/payment-request] fine-grained errors reporting for PaymentAddress (#712) Marcos Cáceres
• Re: [w3c/webpayments-crypto] Should we allow keys or only certificates? (#15) Adrian Hope-Bailie
• Re: [w3c/webpayments-crypto] Should we allow keys or only certificates? (#15) mattsaxon

Monday, 4 June 2018

• Re: [w3c/webpayments-crypto] Mapping between claims and response data elements (#13) ianbjacobs
• Re: [w3c/webpayments-crypto] restructured into steps performed by payment handler and merchant (#16) ianbjacobs
• Re: [w3c/webpayments-crypto] Mapping between claims and response data elements (#13) Peter Saint-Andre
• Re: [w3c/webpayments-crypto] Mapping between claims and response data elements (#13) Adrian Hope-Bailie
• Re: [w3c/webpayments-crypto] Consider Cleartext JWS (#5) Adrian Hope-Bailie
• [w3c/webpayments-crypto] restructured into steps performed by payment handler and merchant (#16) MasterKeyur
• Re: [w3c/webpayments-methods-tokenization] What are various errors related to keys? (#43) ianbjacobs
• Re: [w3c/webpayments-crypto] Mapping between claims and response data elements (#13) ianbjacobs
• Re: [w3c/webpayments-crypto] Consider Cleartext JWS (#5) ianbjacobs
• Re: [w3c/webpayments-crypto] Machine-readable identification of sensitive data to be encrypted? (#11) ianbjacobs
• Re: [w3c/webpayments-crypto] Machine-readable identification of sensitive data to be encrypted? (#11) ianbjacobs
• Re: [w3c/payment-handler] Just in time installation of Payment Handler (#303) ianbjacobs
• Re: [w3c/payment-handler] Just in time installation of Payment Handler (#303) ianbjacobs

Friday, 1 June 2018

• Re: [w3c/webpayments-crypto] Should we allow keys or only certificates? (#15) Peter Saint-Andre
• Re: [w3c/webpayments-crypto] Fixes for key definitions and examples (#14) Wanli Yang
• [w3c/webpayments-crypto] Should we allow keys or only certificates? (#15) Adrian Hope-Bailie
• Re: [w3c/webpayments-crypto] Where to communicate responseEncryptionKey (#6) Adrian Hope-Bailie
• Re: [w3c/webpayments-crypto] Partial vs. full encryption of response data (#7) Adrian Hope-Bailie
• Re: [w3c/webpayments-crypto] Machine-readable identification of sensitive data to be encrypted? (#11) Adrian Hope-Bailie
• Re: [w3c/webpayments-crypto] Mapping between claims and response data elements (#13) Adrian Hope-Bailie
• Re: [w3c/webpayments-crypto] Fixes for key definitions and examples (#14) Adrian Hope-Bailie

Last message date: Saturday, 30 June 2018 16:42:21 UTC