public-webpayments-specs@w3.org from August 2018 by subject

[w3c/3ds] Mixing 3DS with Payment Methods (#9)

[w3c/3ds] Spec feedback (#8)

[w3c/payment-handler] Add paymentRequestID to CanMakePaymentEvent? (#312)

[w3c/payment-handler] Add support for communicating billing address to merchant (e.g., for VAT computation) (#314)

[w3c/payment-handler] Add support for PaymentValidationErrors (#306)

[w3c/payment-handler] Cross-origin iframes and feature policy. (#282)

[w3c/payment-handler] Incorporate the canMakePayment algorithm of the payment method good practices doc. (#313)

[w3c/payment-handler] Need normative text for checking the origin of the SW scope against "supported_origins". (#309)

[w3c/payment-handler] Normative what happens when users closing the window opened by PaymentRequestEvent.openWindow (#299)

[w3c/payment-handler] Payment Handler window `.focused` field (#307)

[w3c/payment-handler] Remove modifiers from CanMakePaymentEvent. (#315)

[w3c/payment-handler] Remove modifiers from CanMakePaymentEvent? (#289)

[w3c/payment-handler] Removed note on payment method manifest and added reference to it (#311)

[w3c/payment-method-basic-card] add: User changes payment method section (#53)

[w3c/payment-request] Add ability to request billing address (#749)

[w3c/payment-request] Add ability to request payer's address (#749)

[w3c/payment-request] Add error member to PaymentValidationErrors (#747)

[w3c/payment-request] Add error reporting billing address (#750)

[w3c/payment-request] Add error reporting for payer address (#750)

[w3c/payment-request] Add generic `error` member for `.retry()` (#729)

[w3c/payment-request] Add paymentMethodErrors, payerErrors, to PaymentDetailsUpdate (#768)

[w3c/payment-request] Add support for merchant validation (#646)

[w3c/payment-request] Add support for merchant validation (#751)

[w3c/payment-request] bless() is racy with document.body (#758)

[w3c/payment-request] Can PaymentMethodChangeEventInit really have a required member? (#770)

[w3c/payment-request] Describe how to implement PaymentAddress.languageCode (#608)

[w3c/payment-request] Drop support for "Push Payments" (#759)

[w3c/payment-request] editorial: mark languageCode at risk (#764)

[w3c/payment-request] fine-grained errors reporting for PaymentAddress (#712)

[w3c/payment-request] fix: default methodName to empty string (#771)

[w3c/payment-request] fix: give PaymentMethodChangeEventInit defaults (#771)

[w3c/payment-request] Mark languageCode at risk (#764)

[w3c/payment-request] Merchant yang ditentukan standar alamat pengiriman (#762)

[w3c/payment-request] Merchant yang ditentukan standar alamat pengiriman (#763)

[w3c/payment-request] Modifiers and [[serializedModifierData]] not actually used anywhere. (#753)

[w3c/payment-request] PaymentDetailsUpdate needs to include payerErrors (#766)

[w3c/payment-request] Proposal to add more details to shopping cart contents and shipping option descriptions (#761)

[w3c/payment-request] Providing an `AbortSignal` instead of calling .abort() (#757)

[w3c/payment-request] Remove PaymentAddress' languageCode (#765)

[w3c/payment-request] Section 3.11 (onpaymentmethodchange attribute) mentions the wrong event interface (#769)

[w3c/payment-request] Should API support billing address capture (for tax computation)? (#27)

[w3c/payment-request] Should the PaymentRequest ID be passed to canMakePayment? (#760)

[w3c/payment-request] Signaling payment handler details errors (#727)

[w3c/payment-request] Suggested emphasis of privacy protections (#628)

[w3c/payment-request] Support fine-grained errors for payment methods (#752)

[w3c/payment-request] Support payment method errors (#749)

[w3c/payment-request] Support requesting billing address (#749)

[w3c/payment-request] teach retry() about payerErrors (#721)

[w3c/payment-request] Update spec to use "event constructing steps" (#767)

[w3c/webpayments-methods-tokenization] Distinguish full tokenized-card from token-reference (lighter payment method) (#46)

[w3c/webpayments-methods-tokenization] How are empty supported* fields to be interpreted? (#48)

[w3c/webpayments-methods-tokenization] Remove supportedCryptogramTypes (#49)

[w3c/webpayments-methods-tokenization] What are the supportedCryptogramTypes? (#47)

Last message date: Friday, 31 August 2018 17:10:30 UTC