public-webpayments-specs@w3.org from September 2020 by subject

[w3c/payment-handler] Collecting use cases that require payment handler window to be 1P context (#370)

[w3c/payment-method-basic-card] Is this a REC-track document? (#88)

[w3c/payment-request] Add dir/lang member on dictionaries whose content is displayed in browser UI (#327)

[w3c/payment-request] Add regionCode attribute to PaymentAddress (1.1) (#836)

[w3c/payment-request] Allow user activation to be delegated to a child frame to trigger request.show() (#917)

[w3c/payment-request] Consume user activation (#916)

[w3c/payment-request] Create azure.yml (#924)

[w3c/payment-request] Deprecate allowpaymentrequest attribute (#928)

[w3c/payment-request] How do the payer and payee agree on the payment obligation as part of the flow? (#113)

[w3c/payment-request] Mark hasEnrolledInstrument() at risk? (#926)

[w3c/payment-request] Proposal: drop `allowpaymentrequest` attribute (#925)

[w3c/payment-request] Remove hasEnrolledInstrument() (#930)

[w3c/payment-request] Remove hasEnrolledInstrument() from version 1.0 (#930)

[w3c/payment-request] Remove merchant validation (#929)

[w3c/payment-request] Richer negotiation re: address redaction? (#842)

[w3c/payment-request] What should we do with MerchantValidationEvent? (#927)

Last message date: Wednesday, 30 September 2020 16:51:02 UTC