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

[w3c/browser-payment-api] "Shown" should be "presented" in prose (#428)

[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] `PaymentInstrument.complete(result)` wording (#402)

[w3c/browser-payment-api] Aborting of in progress push payments (#473)

[w3c/browser-payment-api] Add billing shipping type (#409)

[w3c/browser-payment-api] Add dir/lang member on dictionaries whose content is displayed in browser UI (#327)

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

[w3c/browser-payment-api] Add Guidance Text for User Consent (#229)

[w3c/browser-payment-api] Add payerGivenName + payerFamilyName to PaymentAddress (#480)

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

[w3c/browser-payment-api] Addition of flag on PaymentMethodData to indicate that line items should be shared with apps (#446)

[w3c/browser-payment-api] Ambiguity in "Process payment methods:" (#458)

[w3c/browser-payment-api] API assumes Issuer communication is OOB (#447)

[w3c/browser-payment-api] Badness in constructor... (#459)

[w3c/browser-payment-api] Behavior for multiple modifiers for the same payment method is not defined (#309)

[w3c/browser-payment-api] Changes to show() and canMakePayment() to take into account (#454)

[w3c/browser-payment-api] Clarify wording to not imply 'pull' only payhments (#474)

[w3c/browser-payment-api] Clarify wording to not imply 'pull' only payments (#474)

[w3c/browser-payment-api] Clarity required in section 21.2 regarding (#475)

[w3c/browser-payment-api] complete() does not match all payment apps (#484)

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

[w3c/browser-payment-api] Create pr-preview config file. (#445)

[w3c/browser-payment-api] Define payment option filtering algorithm. (#420)

[w3c/browser-payment-api] Disallow multiple showing payment requests per user agent (#487)

[w3c/browser-payment-api] Does PR API need to include text around matching to take payment method manifest into account? (#478)

[w3c/browser-payment-api] Editorial changes (#465)

[w3c/browser-payment-api] editorial(constructor): remove redundant line (closes #459) (#460)

[w3c/browser-payment-api] editorial: attr/method intros are notes (closes #379) (#438)

[w3c/browser-payment-api] editorial: grouped payment details dictionaries into section (#479)

[w3c/browser-payment-api] editorial: remove redundant event declaration (#469)

[w3c/browser-payment-api] editorial: s/fields/members + xref fixes (closes #424) (#443)

[w3c/browser-payment-api] editorial: s/shown/presented (closes #428) (#435)

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

[w3c/browser-payment-api] feat: put request id in details dictionary (#426)

[w3c/browser-payment-api] Fix constructor handling of shippingType (#452)

[w3c/browser-payment-api] Fix markup errors that broke autopublishing (#444)

[w3c/browser-payment-api] fix(complete): bugus result value will have thrown already (#468)

[w3c/browser-payment-api] fix: change Events section to normative (closes #466) (#489)

[w3c/browser-payment-api] fix: delegate total and error member checks to WebIDL (#425)

[w3c/browser-payment-api] fix: make supportedMethod conforming (#463)

[w3c/browser-payment-api] fix: s/user interaction/transaction (closes #402) (#432)

[w3c/browser-payment-api] Group payment dictionaries into a section (#427)

[w3c/browser-payment-api] How can a user agent not accept a payment method? (#273)

[w3c/browser-payment-api] Initial values for internal slots (#436)

[w3c/browser-payment-api] Introductory explanations of methods should be non-normative notes (#379)

[w3c/browser-payment-api] It is never stated how the payment request ID is used (#415)

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

[w3c/browser-payment-api] Make updateWith() reject the show() promise on validation failures (#451)

[w3c/browser-payment-api] Make updateWith() return a promise signaling any update failures (#418)

[w3c/browser-payment-api] mark currencySystem as feature at risk (#482)

[w3c/browser-payment-api] markup issues (#441)

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

[w3c/browser-payment-api] Move examples to top of document (#456)

[w3c/browser-payment-api] Need to define the interaction of payment API with navigation and browsing context destruction (#360)

[w3c/browser-payment-api] NotSupportedError in private browsing mode (#448)

[w3c/browser-payment-api] PaymentApp fails to abort payment flow (#384)

[w3c/browser-payment-api] PaymentDetails "total" member should be required (#320)

[w3c/browser-payment-api] PaymentDetails should include a transaction ID (#287)

[w3c/browser-payment-api] PaymentRequest does not handle the case of store pickup (#389)

[w3c/browser-payment-api] PaymentRequest type checks (valid non-negative monetary value) (#306)

[w3c/browser-payment-api] PaymentRequestID initialization (#412)

[w3c/browser-payment-api] PaymentResponse attributes should be separate sections (#442)

[w3c/browser-payment-api] Providing/Generating paymentRequestID during construction (#388)

[w3c/browser-payment-api] Recipient and payerName are lacking i18n support (#471)

[w3c/browser-payment-api] Remove trailing comma from IDL enums (#453)

[w3c/browser-payment-api] Request `shippingType` attribute is not defined (#472)

[w3c/browser-payment-api] Section for A11Y Considerations (#450)

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

[w3c/browser-payment-api] Should the user agent generate the `id` when it's empty? (#483)

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

[w3c/browser-payment-api] Should values for supportedNetworks be defined in Basic Card or separately? (#325)

[w3c/browser-payment-api] show() method lacks developer guidance (#461)

[w3c/browser-payment-api] Spec talks about dictionary fields instead of dictionary members (#424)

[w3c/browser-payment-api] Specify how to abort a payment request (#449)

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

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

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

[w3c/browser-payment-api] Supporting push payment methods (#224)

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

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

[w3c/browser-payment-api] updateWith will silently ignore data in hard-to-debug ways (#350)

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

[w3c/browser-payment-api] valid decimal monetary value maybe overly restrictive (#304)

[w3c/browser-payment-api] What does it mean to "accept the payment"? (#278)

[w3c/browser-payment-api] Why are two sections non-normative? (#466)

[w3c/browser-payment-api] Why does PaymentRequest constructor throw on details.error (#302)

[w3c/webpayments-method-identifiers] Add marcoscaceres as collaborator (#24)

[w3c/webpayments-method-identifiers] Add marcosscaceres as collaborator (#24)

[w3c/webpayments-method-identifiers] Check what happens if URL parsing throws.... (#27)

[w3c/webpayments-method-identifiers] chore: tidy (#25)

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

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

[w3c/webpayments-methods-card] Add link to list of card networks (#25)

[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] PaymentResponse missing filters (#28)

[w3c/webpayments-methods-card] PymentResponse missing filters (#28)

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

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

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

[w3c/webpayments-payment-apps-api] Add explicit permission call to allow payment app to handle payments (#94)

[w3c/webpayments-payment-apps-api] Change from clients.openWindow to event.openWindow. (#106)

[w3c/webpayments-payment-apps-api] Different approaches to opening windows (#97)

[w3c/webpayments-payment-apps-api] How can we optimize user experience when there is only one match? (#14)

[w3c/webpayments-payment-apps-api] How does the payee provide information about recommended payment apps? (#79)

[w3c/webpayments-payment-apps-api] Merging from main branch (#112)

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

[w3c/webpayments-payment-apps-api] Need to specify behavior for Clients.openWindow (#73)

[w3c/webpayments-payment-apps-api] Open Window Algorithm (#115)

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

[w3c/webpayments-payment-apps-api] PaymentRequestEvent incompatible with DOM events (#119)

[w3c/webpayments-payment-apps-api] Per 16 March teleconf [1], displayItems are not handed to the payment app (#110)

[w3c/webpayments-payment-apps-api] Proposed changes for #95 (and #96) (#104)

[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] Replace setManifest()/getManifest() with set()/get()/keys()/has()/delete() (#95)

[w3c/webpayments-payment-apps-api] Revisiting payment app filtering (#96)

[w3c/webpayments-payment-apps-api] Run the spec through HTML5-Tidy. (#108)

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

[w3c/webpayments-payment-apps-api] Should `modifiers` be passed to the payment handler? (#118)

[w3c/webpayments-payment-apps-api] Small fixes (#114)

[w3c/webpayments-payment-apps-api] Structural changes based on task force discussion (#107)

[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] Updates for F2F meeting (#113)

[w3c/webpayments-payment-apps-api] Use PaymentRequest and PaymentResponse (#99)

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

[w3c/webpayments-payment-apps-api] Why does a Payment App need to see the line items? (#91)

Last message date: Friday, 31 March 2017 18:12:33 UTC