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

[w3c/payment-handler] Permission model (#363)

[w3c/payment-handler] See W3C TAG review comments (#362)

[w3c/payment-method-basic-card] add requestSecurityCode member to BasicCardRequest (#78)

[w3c/payment-method-basic-card] export definition of `steps to check if a payment can be made` (#86)

[w3c/payment-method-basic-card] Payment request spec references the "Steps to check if a payment can be made" definition which is not exported to xref (#85)

[w3c/payment-request] Allow incremental request of billing and shipping address (#873)

[w3c/payment-request] Editorial: Export terms for payment method basic card spec (#894)

[w3c/payment-request] Editorial: Use respec shorthands instead of `data-lt` (#899)

[w3c/payment-request] Expected behaviours: paymentmethodchange event updates with a rejection (#898)

[w3c/payment-request] Payment Method - BasicCardErrors not showing (working) (#897)

[w3c/payment-request] Payment Method - BasicCardErrors.paymentMethod errors not being displayed (#897)

[w3c/payment-request] Payment Method Basic Card spec uses various Payment Request definitions that Payment Request does not yet export (#890)

[w3c/payment-request] Remove recommendation to localize sheet based on body element (#896)

[w3c/payment-request] Should show() consume user activation? (#886)

[w3c/payment-request] the user interface's language should not be derived from `the body element` (#895)

[w3c/payment-request] Use respec shorthand instead of `data-lt` (#899)

Last message date: Friday, 28 February 2020 04:19:04 UTC