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

[w3c/3ds] Value proposition (#4)

[w3c/payment-handler] "Dispatch e to global" should link (#266)

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

[w3c/payment-handler] chore(PULL_REQUEST_TEMPLATE): add pull request template (#252)

[w3c/payment-handler] chore: tidy up (#274)

[w3c/payment-handler] Consider explaining the connection with payment method manifests sooner (#269)

[w3c/payment-handler] Do not use "context object" (#257)

[w3c/payment-handler] Editorial tweaks to " MethodData Population Algorithm" (#264)

[w3c/payment-handler] Editorial: Fix inconsistent DOMException styles (#271)

[w3c/payment-handler] Fix inconsistent DOMException styles (#271)

[w3c/payment-handler] Fix incorrect destructing in example (#272)

[w3c/payment-handler] Get rid of normative requirements inside dictionary member definitions (#261)

[w3c/payment-handler] How would iDeal work? (#251)

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

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

[w3c/payment-handler] Inconsistent DOMException styles (#267)

[w3c/payment-handler] Incorrect destructing in example (#254)

[w3c/payment-handler] Integrate better with the payment request spec (#258)

[w3c/payment-handler] Move normative requirements on PaymentRequestEvent to the processing model (#262)

[w3c/payment-handler] Normative MUSTs inside a non-normative note (#268)

[w3c/payment-handler] Origin definitions are imprecise (#263)

[w3c/payment-handler] Payment manifest supporting multiple payments apps from different providers? (#270)

[w3c/payment-handler] PaymentInstruments internal storage could be clearer (#256)

[w3c/payment-handler] PaymentInstruments is missing values() and entries() (#255)

[w3c/payment-handler] PaymentManager behavior unclear (#253)

[w3c/payment-handler] Remove requestPermission() (#277)

[w3c/payment-handler] Replace 'enabledMethods' array with 'method' string. (#276)

[w3c/payment-handler] Review userHint (#273)

[w3c/payment-handler] Structured clone usage seems wrong (#265)

[w3c/payment-handler] topLevelOrigin is a weird name (#259)

[w3c/payment-handler] Use the correct origin serialization (#260)

[w3c/payment-handler] Use the correct origin serialization (#275)

[w3c/payment-handler] work in progress: simplification of various things (#247)

[w3c/payment-method-basic-card] Brand selection (#49)

[w3c/payment-method-basic-card] Connecting to payment handler. (#50)

[w3c/payment-method-basic-card] dummy change to trigger travis (#51)

[w3c/payment-request] "User accepts the payment request algorithm" needs to clarify where Payment Handlers are invoked (#476)

[w3c/payment-request] 404 on some tests (#630)

[w3c/payment-request] A distinct invoice address should be supported (#550)

[w3c/payment-request] Add contact info / support URL to show() method? (#687)

[w3c/payment-request] add exclusionList for PaymentAddress (Part 1) (#654)

[w3c/payment-request] Add link to SecureContext test (#697)

[w3c/payment-request] add redactList for PaymentAddress (Part 1) (#654)

[w3c/payment-request] Add region code (Part 2) (#690)

[w3c/payment-request] Add regionCode attribute (#690)

[w3c/payment-request] Add regionCode attribute (Part 2) (#690)

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

[w3c/payment-request] Adding support for private-label credit cards (#662)

[w3c/payment-request] assure request+response use same shippingAddress (9dd14c3)

[w3c/payment-request] Clarify addressLine definition (#676)

[w3c/payment-request] Decide on currencySystem (#617)

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

[w3c/payment-request] Disable Payment Request API in CSP/iframe sandbox (#698)

[w3c/payment-request] Document privacy and security mitigations (#675)

[w3c/payment-request] Editorial: describe security mitigations #675 (#683)

[w3c/payment-request] editorial: fix links to tests (#691)

[w3c/payment-request] fix: unknown currencySystem throws (#689)

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

[w3c/payment-request] PaymentAddress 'region' inconsistencies (#663)

[w3c/payment-request] PaymentOptions.shippingType definition should link to PaymentShippingType, not to itself (#696)

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

[w3c/payment-request] remove currencySystem member (#694)

[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] show() must be triggered by user activation (#655)

[w3c/payment-request] support of VAT (#699)

[w3c/payment-request] test: show() triggered by user activation (#693)

[w3c/payment-request] Unknown currencySystem should throw (#686)

[w3c/payment-request] When "pay" happens, PaymentAddress request and response should match. (#692)

[w3c/payment-request] WIP: add paymentmethodchanged event (#695)

[w3c/webpayments-crypto] Add reference to RFC 7516 (#4)

[w3c/webpayments-crypto] Encrypting to multiple parties (#8)

[w3c/webpayments-crypto] More detailed encryption workflow (#3)

[w3c/webpayments-crypto] Partial vs. full encryption of response data (#7)

[w3c/webpayments-crypto] Required or recommended encryption algorithms (#2)

[w3c/webpayments-crypto] What public key formats are acceptable, and any constraints? (#1)

[w3c/webpayments-crypto] Where to communicate responseEncryptionKey (#6)

[w3c/webpayments-methods-tokenization] Inconsistencies in response example (#37)

[w3c/webpayments-methods-tokenization] Please include example of TokenizedCardResponse (#34)

[w3c/webpayments-methods-tokenization] Token properties? (#25)

Last message date: Friday, 30 March 2018 12:07:41 UTC