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

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

[w3c/payment-handler] Return origin of payment app in PaymentHandlerResponse data? (#217)

[w3c/payment-method-basic-card] Add "store" card support (#46)

[w3c/payment-method-basic-card] Add an excludedFields BasicCardRequest parameter (#29)

[w3c/payment-method-basic-card] Broken link basiccardresponse-member-formats-manual.https.html (#48)

[w3c/payment-method-basic-card] chore(.travis.yml): enable ReSpec validation (#64)

[w3c/payment-method-basic-card] Drop supportedTypes? (#59)

[w3c/payment-method-basic-card] Fixed wrong interface name, links and grammatical errors (#63)

[w3c/payment-method-basic-card] Inconsistent naming of algorithms (#55)

[w3c/payment-method-basic-card] Leave Off Unneeded Information (#5)

[w3c/payment-method-basic-card] Redact more things from billingAddress (#65)

[w3c/payment-method-basic-card] Remove concept of types, supportedTypes, BasicCardType enum (#62)

[w3c/payment-method-basic-card] Things needed to publish as note (#43)

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

[w3c/payment-request] Add PaymentResponse.prototype.onpayerdetailchange (#724)

[w3c/payment-request] Added section and paragraph on accessibility considerations (#802)

[w3c/payment-request] Attach 'payment request is showing boolean' to top-level browsing context (#811)

[w3c/payment-request] Change what canMakePayment() means (#806)

[w3c/payment-request] Clarify the behavior of calling PaymentResponse.complete() while [[retryPromise]] is pending (#795)

[w3c/payment-request] Clarify when the user can abort the payment request algorithm (#796)

[w3c/payment-request] Clarify when the user can abort the payment request algorithm (#810)

[w3c/payment-request] consider requiring an error (non-empty dict) for .retry()? (#792)

[w3c/payment-request] Consider specifying a testing IDL for a mock payment UI (#799)

[w3c/payment-request] De-duplicate "user aborts the payment request" and "abort the update (#814)

[w3c/payment-request] Define PaymentResponse.prototype.retry() method (#720)

[w3c/payment-request] fix: convert PaymentMethodData.data (#812)

[w3c/payment-request] fix: retry()'s errorFields should be optional per WebIDL (#805)

[w3c/payment-request] fix: retry()'s should be optional per WebIDL (#805)

[w3c/payment-request] fix: while retrying complete() returns a rejected promise (#808)

[w3c/payment-request] Follow up on APA Comments on Web Payments FPWDs (#735)

[w3c/payment-request] Include payment handler information in response (#815)

[w3c/payment-request] Meaning of canMakePayment() (#800)

[w3c/payment-request] PaymentMethodData should be converted at construction time (#813)

[w3c/payment-request] Rename `PayerErrorFields` to `PayerErrors` (#789)

[w3c/payment-request] Rethink "payment request is showing" boolean (#809)

[w3c/payment-request] retry(errorFields) should be optional (#804)

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

[w3c/payment-request] Should PaymentMethodData be converted at construction time? (#813)

[w3c/payment-request] Should we put `regionCode` attribute at risk? (#816)

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

[w3c/payment-request] Treat scroll as a user gesture for PaymentRequest.show() (#797)

[w3c/payment-request] Warn when errorFields don't match request[[options]] (#807)

[w3c/payment-request] Way of detecting if can make payment with some instrument (#801)

[w3c/webpayments-methods-tokenization] Should tokenization be a URL-based payment method? (#54)

Last message date: Thursday, 29 November 2018 22:29:06 UTC