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

Adam Solove

• [w3c/3ds] Change `requestLevel` in response to sheet data changes (#6) (Wednesday, 6 June)

Adrian Hope-Bailie

• Re: [w3c/payment-request] Response timeout could leave page/user in confused state. (#737) (Wednesday, 27 June)
• Re: [w3c/webpayments-crypto] Should we allow keys or only certificates? (#15) (Tuesday, 5 June)
• Re: [w3c/webpayments-crypto] Mapping between claims and response data elements (#13) (Monday, 4 June)
• Re: [w3c/webpayments-crypto] Consider Cleartext JWS (#5) (Monday, 4 June)
• [w3c/webpayments-crypto] Should we allow keys or only certificates? (#15) (Friday, 1 June)
• Re: [w3c/webpayments-crypto] Where to communicate responseEncryptionKey (#6) (Friday, 1 June)
• Re: [w3c/webpayments-crypto] Partial vs. full encryption of response data (#7) (Friday, 1 June)
• Re: [w3c/webpayments-crypto] Machine-readable identification of sensitive data to be encrypted? (#11) (Friday, 1 June)
• Re: [w3c/webpayments-crypto] Mapping between claims and response data elements (#13) (Friday, 1 June)
• Re: [w3c/webpayments-crypto] Fixes for key definitions and examples (#14) (Friday, 1 June)

Blake Kaplan

• [w3c/payment-request] Fix a small bug in `abort`'s error handling. (#733) (Wednesday, 20 June)

DannyRussellWP

• Re: [w3c/payment-request] Add PaymentResponse.onpayerdetailchange (#724) (Monday, 18 June)

Domenic Denicola

• Re: [w3c/payment-request] Add PaymentResponse.prototype.onpayerdetailchange (#724) (Thursday, 28 June)
• Re: [w3c/payment-request] Add PaymentResponse.prototype.onpayerdetailchange (#724) (Tuesday, 26 June)
• Re: [w3c/payment-request] Retry request abort the update (#723) (Tuesday, 26 June)
• Re: [w3c/payment-request] Retry request abort the update (#723) (Monday, 25 June)
• Re: [w3c/payment-request] Drop `*Error` from error things (#736) (Monday, 25 June)
• Re: [w3c/payment-request] teach retry() about payerErrors (#721) (Monday, 25 June)
• Re: [w3c/payment-request] Do we need "doc is fully active" checks on `response.complete()`? (#731) (Monday, 25 June)
• Re: [w3c/payment-request] teach retry() about payerErrors (#721) (Monday, 25 June)
• Re: [w3c/payment-request] Editorial: complete() returns rejected promise (#732) (Monday, 25 June)
• Re: [w3c/payment-request] define PaymentResponse.retry() method (#720) (Tuesday, 12 June)
• Re: [w3c/payment-request] add paymentmethodchange event (#695) (Tuesday, 12 June)
• Re: [w3c/payment-request] add paymentmethodchange event (#695) (Wednesday, 6 June)
• Re: [w3c/payment-request] add paymentmethodchange event (#695) (Tuesday, 5 June)
• Re: [w3c/payment-request] fine-grained errors reporting for PaymentAddress (#712) (Tuesday, 5 June)

dtanphat9388

• Re: [w3c/payment-request] payment modifier brings error (#637) (Friday, 22 June)

ianbjacobs

• Re: [w3c/payment-request] Added information about redactList to privacy consideration (#738) (Thursday, 28 June)
• Re: [w3c/payment-request] Added information about redactList to privacy consideration (#738) (Thursday, 28 June)
• [w3c/3ds] User preference for strong authentication (#7) (Wednesday, 27 June)
• [w3c/payment-request] Add secure origin section to security considerations (#742) (Tuesday, 26 June)
• [w3c/payment-request] iframe usage security subsection (#741) (Tuesday, 26 June)
• [w3c/payment-request] document show() protections under security considerations (#740) (Tuesday, 26 June)
• [w3c/payment-request] Added canMakePayment() section to privacy considerations (#739) (Tuesday, 26 June)
• [w3c/payment-request] Added information about redactList to privacy consideration (#738) (Tuesday, 26 June)
• Re: [w3c/payment-request] Response timeout could leave page/user in confused state. (#737) (Tuesday, 26 June)
• Re: [w3c/webpayments-methods-tokenization] How are future card on file transactions supported through dynamic data? (#44) (Tuesday, 26 June)
• Re: [w3c/payment-request] Add PaymentResponse.onpayerdetailchange (#724) (Monday, 25 June)
• Re: [w3c/payment-request] Follow up on APA Comments on Web Payments FPWDs (#735) (Friday, 22 June)
• Re: [w3c/payment-request] editorial: add retry() to state diagram (#734) (Thursday, 21 June)
• Re: [w3c/payment-request] editorial: add retry() to state diagram (#734) (Thursday, 21 June)
• [w3c/webpayments-methods-tokenization] How are future card on file transactions supported through dynamic data? (#44) (Monday, 18 June)
• Re: [w3c/webpayments-methods-tokenization] Token properties? (#25) (Thursday, 14 June)
• Re: [w3c/webpayments-methods-tokenization] Token properties? (#25) (Thursday, 14 June)
• Re: [w3c/webpayments-methods-tokenization] Linkage to BasicCard Spec (#17) (Thursday, 14 June)
• Re: [w3c/webpayments-methods-tokenization] Linkage to BasicCard Spec (#17) (Thursday, 14 June)
• Re: [w3c/webpayments-methods-tokenization] Is billing address required? (#40) (Thursday, 14 June)
• Re: [w3c/webpayments-methods-tokenization] Is billing address required? (#40) (Thursday, 14 June)
• Re: [w3c/webpayments-methods-tokenization] Add PAR to response data? (#38) (Thursday, 14 June)
• Re: [w3c/webpayments-methods-tokenization] Add PAR to response data? (#38) (Thursday, 14 June)
• Re: [w3c/webpayments-methods-tokenization] Add PAR to response data? (#38) (Thursday, 14 June)
• Re: [w3c/webpayments-methods-tokenization] Is cardholderName required? (#42) (Thursday, 14 June)
• Re: [w3c/webpayments-methods-tokenization] Is cardholderName required? (#42) (Thursday, 14 June)
• Re: [w3c/payment-request] Add PaymentResponse.onpayerdetailchange (#724) (Thursday, 14 June)
• Re: [w3c/payment-request] Add PaymentResponse.onpayerdetailchange (#724) (Thursday, 14 June)
• Re: [w3c/payment-request] Always requiring CVV? (#730) (Thursday, 14 June)
• Re: [w3c/payment-request] Retrying a payment (#705) (Thursday, 14 June)
• [w3c/payment-request] Update state diagram to include retry() (#728) (Thursday, 14 June)
• Re: [w3c/payment-request] Signaling payment handler details errors (#727) (Thursday, 14 June)
• Re: [w3c/payment-request] Signaling payment handler details errors (#727) (Thursday, 14 June)
• Re: [w3c/payment-request] Signaling payment handler details errors (#727) (Thursday, 14 June)
• Re: [w3c/3ds] Change `requestLevel` in response to sheet data changes (#6) (Wednesday, 13 June)
• Re: [w3c/3ds] Change `requestLevel` in response to sheet data changes (#6) (Wednesday, 13 June)
• Re: [w3c/webpayments-methods-tokenization] How/whether to handle token sharing use cases (#41) (Tuesday, 12 June)
• Re: [w3c/payment-request] Should API support billing address capture (for tax computation)? (#27) (Tuesday, 12 June)
• Re: [w3c/payment-request] Should API support billing address capture (for tax computation)? (#27) (Tuesday, 12 June)
• Re: [w3c/payment-request] define PaymentResponse.retry() method (#720) (Tuesday, 12 June)
• Re: [w3c/payment-request] fine-grained errors reporting for PaymentAddress (#712) (Wednesday, 6 June)
• Re: [w3c/webpayments-crypto] Mapping between claims and response data elements (#13) (Monday, 4 June)
• Re: [w3c/webpayments-crypto] restructured into steps performed by payment handler and merchant (#16) (Monday, 4 June)
• Re: [w3c/webpayments-methods-tokenization] What are various errors related to keys? (#43) (Monday, 4 June)
• Re: [w3c/webpayments-crypto] Mapping between claims and response data elements (#13) (Monday, 4 June)
• Re: [w3c/webpayments-crypto] Consider Cleartext JWS (#5) (Monday, 4 June)
• Re: [w3c/webpayments-crypto] Machine-readable identification of sensitive data to be encrypted? (#11) (Monday, 4 June)
• Re: [w3c/webpayments-crypto] Machine-readable identification of sensitive data to be encrypted? (#11) (Monday, 4 June)
• Re: [w3c/payment-handler] Just in time installation of Payment Handler (#303) (Monday, 4 June)
• Re: [w3c/payment-handler] Just in time installation of Payment Handler (#303) (Monday, 4 June)

Jake Archibald

• [w3c/payment-handler] Simplifying functional event handling (#305) (Thursday, 21 June)

Kronik-Lilus

• Re: [w3c/payment-request] chore(PULL_REQUEST_TEMPLATE.md): note impact on payment handler (#722) (Saturday, 9 June)
• [w3c/payment-request] chore(PULL_REQUEST_TEMPLATE.md): note impact on payment handler (#722) (Saturday, 9 June)

Krystian Czesak

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

Marcos Cáceres

• Re: [w3c/payment-request] Signaling payment handler details errors (#727) (Saturday, 30 June)
• Re: [w3c/payment-request] Signaling payment handler details errors (#727) (Saturday, 30 June)
• [w3c/payment-method-basic-card] Signaling payment handler details errors (#57) (Saturday, 30 June)
• [w3c/payment-request] EventTarget is used by never linked to (#744) (Thursday, 28 June)
• [w3c/payment-request] [NewObject] annotation (#743) (Thursday, 28 June)
• Re: [w3c/payment-request] Define PaymentResponse.prototype.retry() method (#720) (Thursday, 28 June)
• Re: [w3c/payment-request] Add PaymentResponse.prototype.onpayerdetailchange (#724) (Thursday, 28 June)
• Re: [w3c/payment-request] Add PaymentResponse.prototype.onpayerdetailchange (#724) (Thursday, 28 June)
• Re: [w3c/payment-request] Add PaymentResponse.prototype.onpayerdetailchange (#724) (Thursday, 28 June)
• Re: [w3c/payment-request] Add PaymentResponse.prototype.onpayerdetailchange (#724) (Thursday, 28 June)
• Re: [w3c/payment-request] Add PaymentResponse.prototype.onpayerdetailchange (#724) (Thursday, 28 June)
• Re: [w3c/payment-request] Added information about redactList to privacy consideration (#738) (Thursday, 28 June)
• Re: [w3c/payment-request] Signaling payment handler details errors (#727) (Thursday, 28 June)
• Re: [w3c/payment-request] Add PaymentResponse.prototype.onpayerdetailchange (#724) (Tuesday, 26 June)
• Re: [w3c/payment-request] Signaling payment handler details errors (#727) (Tuesday, 26 June)
• Re: [w3c/payment-request] Retry request abort the update (#723) (Tuesday, 26 June)
• Re: [w3c/payment-request] Retry request abort the update (#723) (Tuesday, 26 June)
• Re: [w3c/payment-request] Response timeout could leave page/user in confused state. (#737) (Tuesday, 26 June)
• Re: [w3c/payment-request] Response timeout could leave page/user in confused state. (#737) (Tuesday, 26 June)
• [w3c/payment-request] Response timeout could leave page/user in confused state. (#737) (Tuesday, 26 June)
• Re: [w3c/payment-request] Retry request abort the update (#723) (Tuesday, 26 June)
• Re: [w3c/payment-request] Add PaymentResponse.onpayerdetailchange (#724) (Monday, 25 June)
• Re: [w3c/payment-request] Retry request abort the update (#723) (Monday, 25 June)
• Re: [w3c/payment-request] Retry request abort the update (#723) (Monday, 25 June)
• Re: [w3c/payment-request] Retry request abort the update (#723) (Monday, 25 June)
• Re: [w3c/payment-request] Retry request abort the update (#723) (Monday, 25 June)
• Re: [w3c/payment-request] Retry request abort the update (#723) (Monday, 25 June)
• Re: [w3c/payment-request] Retry request abort the update (#723) (Monday, 25 June)
• Re: [w3c/payment-request] fix: complete() returns rejected promise (#732) (Monday, 25 June)
• Re: [w3c/payment-request] fix: complete() returns rejected promise (#732) (Monday, 25 June)
• Re: [w3c/payment-request] fix: complete() returns rejected promise (#732) (Monday, 25 June)
• Re: [w3c/payment-request] Retry request abort the update (#723) (Monday, 25 June)
• Re: [w3c/payment-request] fix: complete() returns rejected promise (#732) (Monday, 25 June)
• Re: [w3c/payment-request] Drop `*Error` from error things (#736) (Monday, 25 June)
• Re: [w3c/payment-request] Retry request abort the update (#723) (Monday, 25 June)
• Re: [w3c/payment-request] teach retry() about payerErrors (#721) (Monday, 25 June)
• Re: [w3c/payment-request] teach retry() about payerErrors (#721) (Monday, 25 June)
• [w3c/payment-request] Drop `*Error` from error things (#736) (Monday, 25 June)
• Re: [w3c/payment-request] teach retry() about payerErrors (#721) (Monday, 25 June)
• Re: [w3c/payment-request] teach retry() about payerErrors (#721) (Monday, 25 June)
• Re: [w3c/payment-request] teach retry() about payerErrors (#721) (Monday, 25 June)
• Re: [w3c/payment-request] Add PaymentResponse.onpayerdetailchange (#724) (Monday, 25 June)
• Re: [w3c/payment-request] Follow up on APA Comments on Web Payments FPWDs (#735) (Friday, 22 June)
• [w3c/payment-request] Follow up on APA Comments on Web Payments FPWDs (#735) (Friday, 22 June)
• Re: [w3c/payment-request] editorial: add retry() to state diagram (#734) (Thursday, 21 June)
• Re: [w3c/payment-request] Update state diagram to include retry() (#728) (Thursday, 21 June)
• Re: [w3c/payment-request] Define PaymentResponse.prototype.retry() method (#720) (Thursday, 21 June)
• Re: [w3c/payment-request] add paymentmethodchange event (#695) (Thursday, 21 June)
• Re: [w3c/payment-request] Add equivalent of applepaypaymentmethodchanged (#662) (Thursday, 21 June)
• Re: [w3c/payment-request] add paymentmethodchange event (#695) (Thursday, 21 June)
• Re: [w3c/payment-request] editorial: add retry() to state diagram (#734) (Thursday, 21 June)
• Re: [w3c/payment-request] editorial: add retry() state (#734) (Wednesday, 20 June)
• [w3c/payment-request] editorial: add retry() state (#734) (Wednesday, 20 June)
• Re: [w3c/payment-request] Fix a small bug in `abort`'s error handling. (#733) (Wednesday, 20 June)
• Re: [w3c/payment-request] Fix a small bug in `abort`'s error handling. (#733) (Wednesday, 20 June)
• Re: [w3c/payment-request] Fix a small bug in `abort`'s error handling. (#733) (Wednesday, 20 June)
• Re: [w3c/payment-request] Fix a small bug in `abort`'s error handling. (#733) (Wednesday, 20 June)
• Re: [w3c/payment-request] Define PaymentResponse.prototype.retry() method (#720) (Tuesday, 19 June)
• Re: [w3c/payment-request] Define PaymentResponse.prototype.retry() method (#720) (Tuesday, 19 June)
• Re: [w3c/payment-request] Do we need "doc is fully active" checks on `response.complete()`? (#731) (Tuesday, 19 June)
• [w3c/payment-request] Editorial: complete() returns rejected promise (#732) (Tuesday, 19 June)
• Re: [w3c/payment-request] Define PaymentResponse.prototype.retry() method (#720) (Tuesday, 19 June)
• [w3c/payment-request] Do we need "doc is fully active" checks on `response.complete()`? (#731) (Tuesday, 19 June)
• Re: [w3c/payment-request] Define PaymentResponse.prototype.retry() method (#720) (Monday, 18 June)
• Re: [w3c/payment-request] Define PaymentResponse.prototype.retry() method (#720) (Monday, 18 June)
• Re: [w3c/payment-request] Always requiring CVV? (#730) (Thursday, 14 June)
• Re: [w3c/payment-request] Always requiring CVV? (#730) (Thursday, 14 June)
• Re: [w3c/payment-request] Add PaymentResponse.onpayerdetailchange (#724) (Thursday, 14 June)
• Re: [w3c/payment-request] Add PaymentResponse.onpayerdetailchange (#724) (Thursday, 14 June)
• Re: [w3c/payment-request] Add PaymentResponse.onpayerdetailchange (#724) (Thursday, 14 June)
• Re: [w3c/payment-request] Add PaymentResponse.onpayerdetailchange (#724) (Thursday, 14 June)
• Re: [w3c/payment-request] Add PaymentResponse.onpayerdetailchange (#724) (Thursday, 14 June)
• Re: [w3c/payment-request] Add PaymentResponse.onpayerdetailchange (#724) (Thursday, 14 June)
• Re: [w3c/payment-request] Always requiring CVV? (#730) (Thursday, 14 June)
• [w3c/payment-request] Always requiring CVV? (#730) (Thursday, 14 June)
• [w3c/payment-request] Add generic `error` member for `.retry()` (#729) (Thursday, 14 June)
• Re: [w3c/payment-request] Signaling payment handler details errors (#727) (Thursday, 14 June)
• Re: [w3c/payment-request] Signaling payment handler details errors (#727) (Thursday, 14 June)
• Re: [w3c/payment-request] Should API support billing address capture (for tax computation)? (#27) (Thursday, 14 June)
• [w3c/payment-request] Signaling payment handler details errors (#727) (Thursday, 14 June)
• Re: [w3c/payment-request] define PaymentResponse.retry() method (#720) (Tuesday, 12 June)
• Re: [w3c/payment-request] define PaymentResponse.retry() method (#720) (Tuesday, 12 June)
• Re: [w3c/payment-request] add paymentmethodchange event (#695) (Tuesday, 12 June)
• Re: [w3c/payment-request] Should API support billing address capture (for tax computation)? (#27) (Tuesday, 12 June)
• Re: [w3c/payment-request] Should API support billing address capture (for tax computation)? (#27) (Tuesday, 12 June)
• Re: [w3c/payment-request] define PaymentResponse.retry() method (#720) (Tuesday, 12 June)
• Re: [w3c/payment-request] define PaymentResponse.retry() method (#720) (Tuesday, 12 June)
• Re: [w3c/payment-request] define PaymentResponse.retry() method (#720) (Tuesday, 12 June)
• Re: [w3c/payment-request] define PaymentResponse.retry() method (#720) (Tuesday, 12 June)
• Re: [w3c/payment-request] define PaymentResponse.retry() method (#720) (Tuesday, 12 June)
• Re: [w3c/payment-request] Add explicit extension point to matching algo (#470) (Tuesday, 12 June)
• Re: [w3c/payment-request] Add explicit extension point to matching algo (#470) (Tuesday, 12 June)
• Re: [w3c/payment-request] Should API support billing address capture (for tax computation)? (#27) (Tuesday, 12 June)
• [w3c/payment-request] Editorial: use internal slots (#726) (Tuesday, 12 June)
• Re: [w3c/payment-request] Update test-plan.md after web-platform-tests repo move (#725) (Tuesday, 12 June)
• Re: [w3c/payment-request] Update test-plan.md after web-platform-tests repo move (#725) (Tuesday, 12 June)
• Re: [w3c/payment-request] define PaymentResponse.retry() method (#720) (Tuesday, 12 June)
• Re: [w3c/payment-request] add paymentmethodchange event (#695) (Tuesday, 12 June)
• [w3c/payment-request] Add PaymentResponse.onpayerdetailchange (#724) (Tuesday, 12 June)
• [w3c/payment-request] Retry request abort the update (#723) (Tuesday, 12 June)
• Re: [w3c/payment-request] teach retry() about payerErrors (#721) (Thursday, 7 June)
• Re: [w3c/payment-request] teach retry() about payerErrors (#721) (Thursday, 7 June)
• Re: [w3c/payment-request] teach retry() about payerErrors (#721) (Thursday, 7 June)
• [w3c/payment-request] teach retry() about payerErrors (#721) (Thursday, 7 June)
• Re: [w3c/payment-request] define PaymentResponse.retry() method (#720) (Thursday, 7 June)
• Re: [w3c/payment-request] define PaymentResponse.retry() method (#720) (Thursday, 7 June)
• [w3c/payment-request] define PaymentResponse.retry() method (#720) (Thursday, 7 June)
• Re: [w3c/payment-request] Define PaymentResponse.retry() method (#715) (Wednesday, 6 June)
• Re: [w3c/payment-request] Teach retry() about payerErrors (#716) (Wednesday, 6 June)
• Re: [w3c/payment-request] Define PaymentResponse.retry() method (#715) (Wednesday, 6 June)
• Re: [w3c/payment-request] add paymentmethodchange event (#695) (Wednesday, 6 June)
• Re: [w3c/payment-request] add paymentmethodchange event (#695) (Wednesday, 6 June)
• Re: [w3c/payment-request] add paymentmethodchange event (#695) (Wednesday, 6 June)
• Re: [w3c/payment-request] fine-grained errors reporting for PaymentAddress (#712) (Wednesday, 6 June)
• Re: [w3c/payment-request] Fine grained error recovery for fields (#647) (Wednesday, 6 June)
• Re: [w3c/payment-request] fine-grained errors reporting for PaymentAddress (#712) (Wednesday, 6 June)
• Re: [w3c/payment-request] fine-grained errors reporting for PaymentAddress (#712) (Wednesday, 6 June)
• Re: [w3c/payment-request] fine-grained errors reporting for PaymentAddress (#712) (Wednesday, 6 June)
• Re: [w3c/payment-request] add paymentmethodchange event (#695) (Tuesday, 5 June)
• Re: [w3c/payment-request] add paymentmethodchange event (#695) (Tuesday, 5 June)
• Re: [w3c/payment-request] fine-grained errors reporting for PaymentAddress (#712) (Tuesday, 5 June)

MasterKeyur

• [w3c/webpayments-crypto] restructured into steps performed by payment handler and merchant (#16) (Monday, 4 June)

mattsaxon

• Re: [w3c/webpayments-crypto] Should we allow keys or only certificates? (#15) (Tuesday, 5 June)

Peter Saint-Andre

• Re: [w3c/payment-request] Add PaymentResponse.onpayerdetailchange (#724) (Thursday, 14 June)
• Re: [w3c/payment-request] Add PaymentResponse.onpayerdetailchange (#724) (Thursday, 14 June)
• Re: [w3c/webpayments-crypto] Mapping between claims and response data elements (#13) (Monday, 4 June)
• Re: [w3c/webpayments-crypto] Should we allow keys or only certificates? (#15) (Friday, 1 June)

Philip Jägenstedt

• [w3c/payment-request] Update test-plan.md after web-platform-tests repo move (#725) (Tuesday, 12 June)

tricky456

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

Wanli Yang

• Re: [w3c/payment-request] Add PaymentResponse.onpayerdetailchange (#724) (Monday, 25 June)
• Re: [w3c/webpayments-crypto] Fixes for key definitions and examples (#14) (Friday, 1 June)

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