[w3c/payment-handler] Collecting use cases that require payment handler window to be 1P context (#370)
- Re: [w3c/payment-handler] Collecting use cases that require payment handler window to be 1P context (#370)
- Re: [w3c/payment-handler] Collecting use cases that require payment handler window to be 1P context (#370)
[w3c/payment-request] Passing a transaction id to a payment request (#911)
- Re: [w3c/payment-request] Passing a transaction id to a payment request (#911)
- Re: [w3c/payment-request] Passing a transaction id to a payment request (#911)
Re: [w3c/payment-request] Expected behaviours: paymentmethodchange event updates with a rejection (#898)
- Re: [w3c/payment-request] Expected behaviours: paymentmethodchange event updates with a rejection (#898)
- Re: [w3c/payment-request] Expected behaviours: paymentmethodchange event updates with a rejection (#898)
- Re: [w3c/payment-request] Expected behaviours: paymentmethodchange event updates with a rejection (#898)
- Re: [w3c/payment-request] Expected behaviours: paymentmethodchange event updates with a rejection (#898)
- Re: [w3c/payment-request] Expected behaviours: paymentmethodchange event updates with a rejection (#898)
[w3c/payment-request] Add optional description to PaymentShippingOption (#910)
Re: [w3c/payment-request] Proposal to add optional "description" string field to PaymentShippingOption dictionary (#902)
Re: [w3c/payment-request] Proposal to make the amount field in PaymentShippingOption optional (#901)
[w3c/payment-request] Editorial: Add [[handler]] slot to PaymentRequest (#909)
[w3c/payment-request] fix: disallow duplicate PMIs when created request (#908)
Re: [w3c/payment-request] Give AddressInit's members defaults (#852)
Re: [w3c/payment-request] Move PaymentAddress string defaults to AddressInit (#853)
[w3c/payment-handler] Require user interaction before payment handler response returned (#369)
[w3c/payment-request] Fix typo in code sample. (#907)
- Re: [w3c/payment-request] Fix typo in code sample. (#907)
- Re: [w3c/payment-request] Fix typo in code sample. (#907)
Re: [w3c/payment-handler] Rename canMakePayment* hasEnrolledInstrument (#332)
[w3c/payment-handler] Creating a "Wallet" using PaymentHandler? (#368)
- Re: [w3c/payment-handler] Creating a "Wallet" using PaymentHandler? (#368)
- Re: [w3c/payment-handler] Creating a "Wallet" using PaymentHandler? (#368)
- Re: [w3c/payment-handler] Creating a "Wallet" using PaymentHandler? (#368)
[w3c/payment-handler] chore: tidy (#367)
[w3c/payment-handler] Security consideration: more awareness about cross-origin sharing (#366)
- Re: [w3c/payment-handler] Security consideration: more awareness about cross-origin sharing (#366)
- Re: [w3c/payment-handler] Security consideration: more awareness about cross-origin sharing (#366)
- Re: [w3c/payment-handler] Security consideration: more awareness about cross-origin sharing (#366)
- Re: [w3c/payment-handler] Security consideration: more awareness about cross-origin sharing (#366)
- Re: [w3c/payment-handler] Security consideration: more awareness about cross-origin sharing (#366)
- Re: [w3c/payment-handler] Security consideration: more awareness about cross-origin sharing (#366)
- Re: [w3c/payment-handler] Security consideration: more awareness about cross-origin sharing (#366)
- Re: [w3c/payment-handler] Security consideration: more awareness about cross-origin sharing (#366)
- Re: [w3c/payment-handler] Security consideration: more awareness about cross-origin sharing (#366)
- Re: [w3c/payment-handler] Security consideration: more awareness about cross-origin sharing (#366)
- Re: [w3c/payment-handler] Security consideration: more awareness about cross-origin sharing (#366)
- Re: [w3c/payment-handler] Security consideration: more awareness about cross-origin sharing (#366)
- Re: [w3c/payment-handler] Security consideration: more awareness about cross-origin sharing (#366)
[w3c/payment-handler] Security consideration: user consent before payment (#365)
- Re: [w3c/payment-handler] Security consideration: user consent before payment (#365)
- Re: [w3c/payment-handler] Security consideration: user consent before payment (#365)
- Re: [w3c/payment-handler] Security consideration: user consent before payment (#365)
- Re: [w3c/payment-handler] Security consideration: user consent before payment (#365)
- Re: [w3c/payment-handler] Security consideration: user consent before payment (#365)
- Re: [w3c/payment-handler] Security consideration: user consent before payment (#365)
- Re: [w3c/payment-handler] Security consideration: user consent before payment (#365)
- Re: [w3c/payment-handler] Security consideration: user consent before payment (#365)
- Re: [w3c/payment-handler] Security consideration: user consent before payment (#365)
- Re: [w3c/payment-handler] Security consideration: user consent before payment (#365)
- Re: [w3c/payment-handler] Security consideration: user consent before payment (#365)
- Re: [w3c/payment-handler] Security consideration: user consent before payment (#365)
[w3c/payment-handler] Rename canmakepayment event to hasenrolledinstrument event (#364)
Re: [w3c/payment-handler] Open Window Algorithm and tracking through 1ps (#351)
- Re: [w3c/payment-handler] Open Window Algorithm and tracking through 1ps (#351)
- Re: [w3c/payment-handler] Open Window Algorithm and tracking through 1ps (#351)
- Re: [w3c/payment-handler] Open Window Algorithm and tracking through 1ps (#351)
- Re: [w3c/payment-handler] Open Window Algorithm and tracking through 1ps (#351)
- Re: [w3c/payment-handler] Open Window Algorithm and tracking through 1ps (#351)
- Re: [w3c/payment-handler] Open Window Algorithm and tracking through 1ps (#351)
- Re: [w3c/payment-handler] Open Window Algorithm and tracking through 1ps (#351)
Re: [w3c/payment-handler] Shipping Address and Payer's Contact info Delegation (#349)
Re: [w3c/payment-handler] Updated examples.md - Formatting (#357)
[w3c/payment-request] Privacy considerations concerning shipping cost calculation (#906)
- Re: [w3c/payment-request] Privacy considerations concerning shipping cost calculation (#906)
- Re: [w3c/payment-request] Privacy considerations concerning shipping cost calculation (#906)
- Re: [w3c/payment-request] Privacy considerations concerning shipping cost calculation (#906)
[w3c/payment-request] Disallow ambiguous methodData declarations? (#905)
- Re: [w3c/payment-request] Disallow ambiguous methodData declarations? (#905)
- Re: [w3c/payment-request] Disallow ambiguous methodData declarations? (#905)
- Re: [w3c/payment-request] Disallow ambiguous methodData declarations? (#905)
[w3c/payment-request] Clarification on payment handler selection in spec (#904)
[w3c/payment-request] Discuss findings of security analysis (#903)
- Re: [w3c/payment-request] Discuss findings of security analysis (#903)
- Re: [w3c/payment-request] Discuss findings of security analysis (#903)
- Re: [w3c/payment-request] Discuss findings of security analysis (#903)
- Re: [w3c/payment-request] Discuss findings of security analysis (#903)
- Re: [w3c/payment-request] Discuss findings of security analysis (#903)