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

[w3c/payment-handler] "Convert image objects" trashes all images (#235)

[w3c/payment-handler] Add AbortPaymentEvent. (#207)

[w3c/payment-handler] Add CanMakePaymentEvent. (#170)

[w3c/payment-handler] Editorial: Simplify abstract (#225)

[w3c/payment-handler] Editorial: small fixes, redundancies (#228)

[w3c/payment-handler] Editorial: trim introduction (#227)

[w3c/payment-handler] Editorial: trim/relocate conformance (#226)

[w3c/payment-handler] fix: PaymentInstruments.get not exceptional (#231)

[w3c/payment-handler] Image fetching does not seem to be defined (#237)

[w3c/payment-handler] ImageObjects can now reference ImageResource (#238)

[w3c/payment-handler] Just-in-time payment handler install (#240)

[w3c/payment-handler] Only allows instrument.set() in active service worker (#224)

[w3c/payment-handler] PaymentInstruments .set() and icons (#233)

[w3c/payment-handler] PaymentInstruments' "the collection" needs an internal slot. (#232)

[w3c/payment-handler] Per Tommy, mark him as former editor (#222)

[w3c/payment-handler] Remove 'Origin and Instrument Display for Selection' sections (#229)

[w3c/payment-handler] retrieving the permission state (#234)

[w3c/payment-handler] SW registration code unclear/incorrect (#223)

[w3c/payment-handler] Trying to get a non-existing value is not exceptional (#230)

[w3c/payment-handler] UI testing (#221)

[w3c/payment-handler] User consent and permissions (#239)

[w3c/payment-handler] What happens when clearing site data? (#236)

[w3c/payment-method-basic-card] fix: define how to set billingAddress (closes #44) (#45)

[w3c/payment-method-basic-card] When creating the billing address, hook into construction of payment address algo from payment request (#44)

[w3c/payment-request] Add localization hint for payment sheet (#656)

[w3c/payment-request] Add way to update `total` and `displayItems` after `.show()` but before user interaction (#645)

[w3c/payment-request] Add way to update `total` and `displayItems` before `.show()` (#639)

[w3c/payment-request] Allow locale to be specified by the developer. (#650)

[w3c/payment-request] Consistent requirement for when `.show()` can be called. (#651)

[w3c/payment-request] Editorial: define create a PaymentAddress algo (#644)

[w3c/payment-request] fine grained error recovery for fields (#647)

[w3c/payment-request] If a card payment fails, should we support exclusion of that card instrument from matching? (#237)

[w3c/payment-request] Implementation of PaymentAddress.languageCode (#608)

[w3c/payment-request] Make Payment Address construction into it's own sub algorithm (#643)

[w3c/payment-request] Make Payment Address construction into its own sub algorithm (#643)

[w3c/payment-request] Merchant validation (#646)

[w3c/payment-request] Merchant-specified default shipping address (#653)

[w3c/payment-request] redact full shipping address from event until payment response (#648)

[w3c/payment-request] Require user gesture when `.show()` is called (#651)

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

[w3c/payment-request] should PaymentDetailsUpdate merge with existing data (#649)

[w3c/payment-request] Should PaymentItems have a type? (#163)

[w3c/payment-request] show() must be triggered by user activation (#655)

[w3c/payment-request] Standardize phone number format (#652)

[w3c/payment-request] WIP: add constructor to PaymentAddress (#654)

[w3c/webpayments-methods-tokenization] Generalisation of Encrypted Card (#22)

[w3c/webpayments-methods-tokenization] multiuse flow (#20)

[w3c/webpayments-methods-tokenization] Need for environment parameter (#19)

[w3c/webpayments-methods-tokenization] Should the tokenization task force standardize an interface between payment apps and tokenization service providers? (#14)

[w3c/webpayments-methods-tokenization] What to do if tokenized data looks like basic card data? (#21)

[w3c/webpayments-methods-tokenization] Where does tokenisation occur in the the flow - and do we care (#16)

Last message date: Thursday, 30 November 2017 23:09:32 UTC