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

[w3c/browser-payment-api] "User accepts payment request" algorithm should timeout without .complete(). (#508)

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

[w3c/browser-payment-api] 'Interactive' Bias in API (#467)

[w3c/browser-payment-api] 'Pull' Payment Bias in API spec (#499)

[w3c/browser-payment-api] Add explicit extension point to matching algo (#470)

[w3c/browser-payment-api] Add extension point (#492)

[w3c/browser-payment-api] Add postMessage() and addMessageListener() for enabling "in-bound" communication (#494)

[w3c/browser-payment-api] Added BCP ref (#510)

[w3c/browser-payment-api] Adding legal entity types for consistency (#491)

[w3c/browser-payment-api] canMakePayment() might be in the wrong place? (#403)

[w3c/browser-payment-api] Clarify use of API in (or not in) Secure Contexts (#501)

[w3c/browser-payment-api] Consider adding examples of payment matching algorithm (#498)

[w3c/browser-payment-api] Consider removing merchant preference language (#481)

[w3c/browser-payment-api] Define expected behavior when no 'shippingaddresschange ' event listener is defined (#507)

[w3c/browser-payment-api] Editorial: consider removing merchant preference language (#506)

[w3c/browser-payment-api] Editorial: event `.target` attribute should be relatedTarget (#513)

[w3c/browser-payment-api] Editorial: paymentResponse.complete() should return a rejected promise, not throw (#509)

[w3c/browser-payment-api] editorial: s/target/request in updateWith() algo (#516)

[w3c/browser-payment-api] editorial: s/target/request in updateWith() algo (#517)

[w3c/browser-payment-api] editorial: use DOM relatedTarget instead of .target (closes #513) (#515)

[w3c/browser-payment-api] editorial: xref EventInit in DOM spec (#514)

[w3c/browser-payment-api] Editors to figure out text on line items (#477)

[w3c/browser-payment-api] Edits for issue 481 (#506)

[w3c/browser-payment-api] fix: broken links to HTML (closes #502) (#504)

[w3c/browser-payment-api] l10n: adds Localizable dict + TextDirection enum (closes #327) (#455)

[w3c/browser-payment-api] Links to some HTML definitions are broken (#502)

[w3c/browser-payment-api] maybe add `DisplayItem` dictionary (#457)

[w3c/browser-payment-api] Missing (normative) reference to BPC-47 (language code) (#503)

[w3c/browser-payment-api] Payment App or Payment Handler language (#497)

[w3c/browser-payment-api] PaymentAddress and null values (#495)

[w3c/browser-payment-api] Provide better mapping between PaymentAddress and HTML5 autofill (#505)

[w3c/browser-payment-api] Redo PR 506 (on merchant prefs) (#518)

[w3c/browser-payment-api] Reference to payment apps in Introduction needs updating (#496)

[w3c/browser-payment-api] Reject with SecurityError if the UA rejects the call to show(). (#512)

[w3c/browser-payment-api] Remove 2119 language from privacy section. (#511)

[w3c/browser-payment-api] ShippingAddress and null values (#495)

[w3c/browser-payment-api] should .show() be user gated? (#486)

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

[w3c/browser-payment-api] Should user agent validate currency? (#490)

[w3c/browser-payment-api] Standardize on "Payer" and "Payee" terms (#493)

[w3c/browser-payment-api] State change issues in updateWith() (#500)

[w3c/browser-payment-api] Supplement QuoteExceededError with NotAllowedError for canMakePayments (#485)

[w3c/browser-payment-api] supportedMethods (URL and DOMString) (#464)

[w3c/browser-payment-api] Unclear what happens when multiple PRs call show() (#462)

[w3c/browser-payment-api] Use "NotAllowedError" instead of "QuotaExceededError" (#488)

[w3c/webpayments-method-identifiers] "W3C String" is overly generic (#32)

[w3c/webpayments-method-identifiers] [SECURE-CONTEXTS] should be a normative rather than informative reference (#29)

[w3c/webpayments-method-identifiers] Circular dependency between PMI and PR specs (#22)

[w3c/webpayments-method-identifiers] citation to dated version of since-abandoned url spec fork is unusual (#30)

[w3c/webpayments-method-identifiers] editorial: rm 'Conditional Matching Beyond Payment Methods' section (#36)

[w3c/webpayments-method-identifiers] feat: rewrite all the things (#35)

[w3c/webpayments-method-identifiers] If URL parsing fails then always fail to match URLs. (#31)

[w3c/webpayments-method-identifiers] Link to registry of W3C-published short strings (#26)

[w3c/webpayments-method-identifiers] Payment Method Identifier needs dfn (#23)

[w3c/webpayments-method-identifiers] Remove "Conditional Matching Beyond Payment Method Identifier Matching" (#34)

[w3c/webpayments-method-identifiers] Removed wording about overloading identifiers (#33)

[w3c/webpayments-method-identifiers] SRI on manifest (#18)

[w3c/webpayments-method-identifiers] use of 'must' in section on Syntax of URLs as Payment Method Identifiers is suspicious (#28)

[w3c/webpayments-method-identifiers] Why are payment ids restricted to [a-z0-9]? (#20)

[w3c/webpayments-methods-card] Add an excludedFields BasicCardRequest parameter (#29)

[w3c/webpayments-methods-card] Add text about why the api can reduce need to store credit card information (#18)

[w3c/webpayments-methods-card] Clarify the required behaviour for options parameters (#26)

[w3c/webpayments-methods-card] Clarify this specification is intended to become a W3C Note (#27)

[w3c/webpayments-methods-card] Leave Off Unneeded Information (#5)

[w3c/webpayments-methods-card] list/registry of approved card network identifiers should be listed in references section (#32)

[w3c/webpayments-methods-card] No description of BasicCardResponse's billingAddress (#30)

[w3c/webpayments-methods-card] Say how we integrate with PaymentRequest (#23)

[w3c/webpayments-methods-card] security and privacy considerations section seems insufficient (#31)

[w3c/webpayments-methods-card] What if the card type is unknown by the payment app? (#19)

[w3c/webpayments-payment-apps-api] [Editorial] Clean up respec errors (#122)

[w3c/webpayments-payment-apps-api] [Privacy] Clarify what information user agents forget at various moments (#124)

[w3c/webpayments-payment-apps-api] `appRequest` attribute should not be a dictionary (#111)

[w3c/webpayments-payment-apps-api] Add .clear() to map-likes (#129)

[w3c/webpayments-payment-apps-api] Add support for topLevelOrigin and paymentRequestOrigin (#130)

[w3c/webpayments-payment-apps-api] Define event handler before payment manager (#134)

[w3c/webpayments-payment-apps-api] Diagrams (#132)

[w3c/webpayments-payment-apps-api] Display may be subject to user and local policy (consider UA making security decisions etc) (#5)

[w3c/webpayments-payment-apps-api] Do we need "Payment Manager" and "Payment Handler"? (#127)

[w3c/webpayments-payment-apps-api] Image object is undefined (#125)

[w3c/webpayments-payment-apps-api] Issue marker cleanup (#133)

[w3c/webpayments-payment-apps-api] Multiple payment apps per origin (#98)

[w3c/webpayments-payment-apps-api] Origin should include iframe(s) (#120)

[w3c/webpayments-payment-apps-api] Pictures would help! (#49)

[w3c/webpayments-payment-apps-api] Recommended payment apps (#74)

[w3c/webpayments-payment-apps-api] Relation between merchant order of payment methods and payment app order of instruments (#116)

[w3c/webpayments-payment-apps-api] Renaming PaymentApp* classes (#109)

[w3c/webpayments-payment-apps-api] Respec fixes (#126)

[w3c/webpayments-payment-apps-api] Respect fixes (#126)

[w3c/webpayments-payment-apps-api] Revisit Examples 3 and 4 (#128)

[w3c/webpayments-payment-apps-api] Share user data with Payment App (#123)

[w3c/webpayments-payment-apps-api] Support for Abort() being delegated to Payment Handler (#117)

[w3c/webpayments-payment-apps-api] The instrumnets/wallets attributes should be readonly and [SameObject]. (#121)

[w3c/webpayments-payment-apps-api] WebIDL fix (#131)

[w3c/webpayments-payment-apps-api] What does "icon" mean? (#69)

[w3c/webpayments-payment-apps-api] What is a Payment App? (#105)

[w3c/webpayments-payment-handler] Define event handler before payment manager (#134)

[w3c/webpayments-payment-handler] Do we need "Payment Manager" and "Payment Handler"? (#127)

[w3c/webpayments-payment-handler] Editorial changes for FPWD (#138)

[w3c/webpayments-payment-handler] Improve payment app arch image (#140)

[w3c/webpayments-payment-handler] Merge PaymentAppResponse and PaymentRequestEvent (#142)

[w3c/webpayments-payment-handler] Passing modifiers to payment apps (#139)

[w3c/webpayments-payment-handler] respec fix (#141)

[w3c/webpayments-payment-handler] Tidy (#137)

[w3c/webpayments-payment-handler] Update README.md to link to new repo (#135)

[w3c/webpayments-payment-handler] Updated short name and URL for new repo name (#136)

Last message date: Friday, 28 April 2017 15:51:41 UTC