public-webpayments-specs@w3.org from April 2020 by author

Adrian Hope-Bailie

• Re: [w3c/payment-handler] Collecting use cases that require payment handler window to be 1P context (#370) (Thursday, 30 April)

Anders Rundgren

• Re: [w3c/payment-handler] Creating a "Wallet" using PaymentHandler? (#368) (Saturday, 18 April)
• [w3c/payment-handler] Creating a "Wallet" using PaymentHandler? (#368) (Saturday, 18 April)
• Re: [w3c/payment-handler] Open Window Algorithm and tracking through 1ps (#351) (Wednesday, 15 April)
• Re: [w3c/payment-handler] Open Window Algorithm and tracking through 1ps (#351) (Thursday, 9 April)
• Re: [w3c/payment-handler] Open Window Algorithm and tracking through 1ps (#351) (Wednesday, 8 April)
• Re: [w3c/payment-request] Discuss findings of security analysis (#903) (Wednesday, 1 April)

crowgames

• Re: [w3c/payment-request] Privacy considerations concerning shipping cost calculation (#906) (Wednesday, 29 April)
• Re: [w3c/payment-request] Discuss findings of security analysis (#903) (Wednesday, 1 April)
• Re: [w3c/payment-request] Discuss findings of security analysis (#903) (Wednesday, 1 April)
• [w3c/payment-request] Privacy considerations concerning shipping cost calculation (#906) (Wednesday, 1 April)
• [w3c/payment-request] Disallow ambiguous methodData declarations? (#905) (Wednesday, 1 April)
• [w3c/payment-request] Clarification on payment handler selection in spec (#904) (Wednesday, 1 April)
• [w3c/payment-request] Discuss findings of security analysis (#903) (Wednesday, 1 April)

Danyao Wang

• [w3c/payment-handler] Collecting use cases that require payment handler window to be 1P context (#370) (Thursday, 30 April)
• Re: [w3c/payment-handler] Security consideration: more awareness about cross-origin sharing (#366) (Monday, 27 April)
• Re: [w3c/payment-handler] Security consideration: user consent before payment (#365) (Monday, 27 April)
• Re: [w3c/payment-handler] Require user interaction before payment handler response returned (#369) (Wednesday, 22 April)
• Re: [w3c/payment-handler] Security consideration: more awareness about cross-origin sharing (#366) (Wednesday, 22 April)
• Re: [w3c/payment-handler] Security consideration: more awareness about cross-origin sharing (#366) (Tuesday, 21 April)
• Re: [w3c/payment-handler] Security consideration: user consent before payment (#365) (Tuesday, 21 April)
• Re: [w3c/payment-handler] Security consideration: more awareness about cross-origin sharing (#366) (Thursday, 16 April)
• Re: [w3c/payment-handler] Security consideration: user consent before payment (#365) (Thursday, 16 April)
• Re: [w3c/payment-handler] Security consideration: user consent before payment (#365) (Thursday, 16 April)
• Re: [w3c/payment-handler] chore: tidy (#367) (Thursday, 16 April)
• Re: [w3c/payment-handler] Security consideration: user consent before payment (#365) (Thursday, 16 April)
• Re: [w3c/payment-handler] Rename canmakepayment event to hasenrolledinstrument event (#364) (Tuesday, 14 April)
• [w3c/payment-handler] Rename canmakepayment event to hasenrolledinstrument event (#364) (Tuesday, 14 April)
• Re: [w3c/payment-handler] Open Window Algorithm and tracking through 1ps (#351) (Wednesday, 8 April)
• Re: [w3c/payment-handler] Open Window Algorithm and tracking through 1ps (#351) (Wednesday, 8 April)

Eiji Kitamura

• Re: [w3c/payment-request] Passing a transaction id to a payment request (#911) (Wednesday, 29 April)
• [w3c/payment-request] Passing a transaction id to a payment request (#911) (Tuesday, 28 April)

ianbjacobs

• Re: [w3c/payment-request] Passing a transaction id to a payment request (#911) (Tuesday, 28 April)
• Re: [w3c/payment-handler] Security consideration: more awareness about cross-origin sharing (#366) (Monday, 27 April)
• Re: [w3c/payment-handler] Security consideration: user consent before payment (#365) (Monday, 27 April)
• Re: [w3c/payment-request] Disallow ambiguous methodData declarations? (#905) (Monday, 27 April)
• Re: [w3c/payment-handler] Security consideration: more awareness about cross-origin sharing (#366) (Wednesday, 22 April)
• Re: [w3c/payment-handler] Security consideration: more awareness about cross-origin sharing (#366) (Wednesday, 22 April)
• Re: [w3c/payment-handler] Security consideration: user consent before payment (#365) (Wednesday, 22 April)
• [w3c/payment-handler] Require user interaction before payment handler response returned (#369) (Wednesday, 22 April)
• Re: [w3c/payment-handler] Security consideration: user consent before payment (#365) (Wednesday, 22 April)
• Re: [w3c/payment-request] Disallow ambiguous methodData declarations? (#905) (Tuesday, 21 April)
• Re: [w3c/payment-handler] Rename canMakePayment* hasEnrolledInstrument (#332) (Monday, 20 April)
• Re: [w3c/payment-handler] Rename canMakePayment* hasEnrolledInstrument (#332) (Monday, 20 April)
• Re: [w3c/payment-handler] Creating a "Wallet" using PaymentHandler? (#368) (Saturday, 18 April)
• Re: [w3c/payment-handler] Creating a "Wallet" using PaymentHandler? (#368) (Saturday, 18 April)
• Re: [w3c/payment-handler] Security consideration: more awareness about cross-origin sharing (#366) (Thursday, 16 April)
• Re: [w3c/payment-handler] Security consideration: user consent before payment (#365) (Thursday, 16 April)
• Re: [w3c/payment-handler] Security consideration: user consent before payment (#365) (Thursday, 16 April)
• Re: [w3c/payment-handler] Security consideration: more awareness about cross-origin sharing (#366) (Thursday, 16 April)
• Re: [w3c/payment-handler] Security consideration: more awareness about cross-origin sharing (#366) (Thursday, 16 April)
• [w3c/payment-handler] Security consideration: more awareness about cross-origin sharing (#366) (Wednesday, 15 April)
• [w3c/payment-handler] Security consideration: user consent before payment (#365) (Wednesday, 15 April)
• Re: [w3c/payment-handler] Open Window Algorithm and tracking through 1ps (#351) (Wednesday, 8 April)
• Re: [w3c/payment-request] Discuss findings of security analysis (#903) (Wednesday, 1 April)

Jinho Bang

• Re: [w3c/payment-handler] Security consideration: user consent before payment (#365) (Friday, 17 April)

Marcos Cáceres

• Re: [w3c/payment-handler] Collecting use cases that require payment handler window to be 1P context (#370) (Thursday, 30 April)
• Re: [w3c/payment-request] Privacy considerations concerning shipping cost calculation (#906) (Wednesday, 29 April)
• Re: [w3c/payment-handler] Security consideration: more awareness about cross-origin sharing (#366) (Monday, 27 April)
• Re: [w3c/payment-request] Expected behaviours: paymentmethodchange event updates with a rejection (#898) (Monday, 27 April)
• Re: [w3c/payment-request] Expected behaviours: paymentmethodchange event updates with a rejection (#898) (Monday, 27 April)
• Re: [w3c/payment-request] Expected behaviours: paymentmethodchange event updates with a rejection (#898) (Monday, 27 April)
• Re: [w3c/payment-request] Expected behaviours: paymentmethodchange event updates with a rejection (#898) (Monday, 27 April)
• Re: [w3c/payment-request] Proposal to add optional "description" string field to PaymentShippingOption dictionary (#902) (Monday, 27 April)
• [w3c/payment-request] Add optional description to PaymentShippingOption (#910) (Monday, 27 April)
• Re: [w3c/payment-request] Proposal to add optional "description" string field to PaymentShippingOption dictionary (#902) (Monday, 27 April)
• Re: [w3c/payment-request] Proposal to make the amount field in PaymentShippingOption optional (#901) (Monday, 27 April)
• [w3c/payment-request] Editorial: Add [[handler]] slot to PaymentRequest (#909) (Monday, 27 April)
• Re: [w3c/payment-request] Privacy considerations concerning shipping cost calculation (#906) (Monday, 27 April)
• [w3c/payment-request] fix: disallow duplicate PMIs when created request (#908) (Monday, 27 April)
• Re: [w3c/payment-request] Give AddressInit's members defaults (#852) (Monday, 27 April)
• Re: [w3c/payment-request] Give AddressInit's members defaults (#852) (Monday, 27 April)
• Re: [w3c/payment-request] Move PaymentAddress string defaults to AddressInit (#853) (Monday, 27 April)
• Re: [w3c/payment-request] Fix typo in code sample. (#907) (Wednesday, 22 April)
• Re: [w3c/payment-request] Fix typo in code sample. (#907) (Wednesday, 22 April)
• Re: [w3c/payment-request] Disallow ambiguous methodData declarations? (#905) (Wednesday, 22 April)
• Re: [w3c/payment-handler] chore: tidy (#367) (Friday, 17 April)
• Re: [w3c/payment-handler] Security consideration: user consent before payment (#365) (Thursday, 16 April)
• Re: [w3c/payment-handler] Security consideration: more awareness about cross-origin sharing (#366) (Thursday, 16 April)
• Re: [w3c/payment-handler] Security consideration: more awareness about cross-origin sharing (#366) (Thursday, 16 April)
• [w3c/payment-handler] chore: tidy (#367) (Thursday, 16 April)
• Re: [w3c/payment-handler] Shipping Address and Payer's Contact info Delegation (#349) (Thursday, 2 April)
• Re: [w3c/payment-handler] Updated examples.md - Formatting (#357) (Thursday, 2 April)
• Re: [w3c/payment-handler] Updated examples.md - Formatting (#357) (Thursday, 2 April)
• Re: [w3c/payment-request] Discuss findings of security analysis (#903) (Wednesday, 1 April)

MaxG

• Re: [w3c/payment-request] Expected behaviours: paymentmethodchange event updates with a rejection (#898) (Monday, 27 April)

pes

• Re: [w3c/payment-handler] Open Window Algorithm and tracking through 1ps (#351) (Wednesday, 8 April)
• Re: [w3c/payment-handler] Open Window Algorithm and tracking through 1ps (#351) (Wednesday, 8 April)

Rouslan Solomakhin

• Re: [w3c/payment-request] Expected behaviours: paymentmethodchange event updates with a rejection (#898) (Monday, 27 April)
• [w3c/payment-request] Fix typo in code sample. (#907) (Wednesday, 22 April)

Sahel Sharify

• Re: [w3c/payment-handler] Shipping Address and Payer's Contact info Delegation (#349) (Friday, 17 April)

Last message date: Thursday, 30 April 2020 16:06:54 UTC