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

[w3c/payment-handler] `requestPermission` is static in Web IDL but example is not (#198)

[w3c/payment-handler] Add "Validate Methods Algorithm" (#197)

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

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

[w3c/payment-handler] Add link to payment handler test suite (#210)

[w3c/payment-handler] Add userHint to PaymentManager (#206)

[w3c/payment-handler] Change openWindow algorithm 14.1 to 'Resolve promise with null.' (#201)

[w3c/payment-handler] Clarify empty instrument key meaning. (#208)

[w3c/payment-handler] Default handler icon? (#178)

[w3c/payment-handler] Define PaymentRequestEvent.respondWith() behavior. (#194)

[w3c/payment-handler] Don't check PaymentRequest.[[state]] in openWindow() algorithm. (#196)

[w3c/payment-handler] Establish Editorial process (#156)

[w3c/payment-handler] Fix a example for PaymentManager.requestPermission(). (#199)

[w3c/payment-handler] Make explicit which origin to use in conjunction with payment method manifest (#203)

[w3c/payment-handler] Make explicit which origin to use in conjunction with payment method manifest. (#209)

[w3c/payment-handler] move dependency section down, as is done in PR API (#211)

[w3c/payment-handler] Registration example accesses `registration` before it is defined (#200)

[w3c/payment-handler] Resolve with null instead of reject with 'SecurityError' if PaymentRequestEvent.openWindow is opened in a different origin (#202)

[w3c/payment-handler] Return null after the window is opened instead of reject with 'SecurityError' (#202)

[w3c/payment-handler] Revisiting Payment Method specific filter/capability matching (#157)

[w3c/payment-handler] Simplify Payment Handler Registration example. (#204)

[w3c/payment-handler] Stop committing things without tests (#205)

[w3c/payment-handler] Suggestion: replace `PaymentWallets` with a property on `PaymentInstrument` (#153)

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

[w3c/payment-handler] The Open Window Algorithm tries to access [[state]] of a request in a way that doesn't make sense (#192)

[w3c/payment-handler] tweak about usage (93e90af)

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

[w3c/payment-method-basic-card] Adding support for "encrypted basic card" (#38)

[w3c/payment-method-basic-card] Define processing model (#39)

[w3c/payment-method-basic-card] No description of BasicCardResponse's billingAddress (#30)

[w3c/payment-method-basic-card] Relationship to PaymentRequest (#40)

[w3c/payment-method-basic-card] Say how we integrate with PaymentRequest (#23)

[w3c/payment-method-basic-card] Unclear what happens when there are duplicates? (#36)

[w3c/payment-method-basic-card] WIP: Processing model (#39)

[w3c/payment-method-id] Better define validity of standardized PMIs? (#48)

[w3c/payment-method-id] Better defined validity of standardized PMIs? (#48)

[w3c/payment-method-id] CR checklist (#39)

[w3c/payment-method-id] Define generalized PMI validator (#44)

[w3c/payment-method-id] Define syntax of standard PMI (closes #48) (#49)

[w3c/payment-method-id] editorial: add CR exit criteria (#42)

[w3c/payment-method-id] Editorial: final round of prep for CR (closes #39) (#45)

[w3c/payment-method-id] make fetching URL-PMI optional (closes #33) (#40)

[w3c/payment-method-id] Other specs must define validity rules (closes #46) (#47)

[w3c/payment-method-id] Reference manifest spec (#33)

[w3c/payment-method-id] w3c.github.io/payment-method-id/ is not in parity with the tests (#46)

[w3c/payment-request] .updateWith() should only be callable if event was canceled (#589)

[w3c/payment-request] .updateWith() should only be callable if event was cancelled (#589)

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

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

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

[w3c/payment-request] Add section on Payment Handler Matching (#582)

[w3c/payment-request] Adding support for "encrypted basic card" (#572)

[w3c/payment-request] After CR, evaluate if paymentRequest.id being a UUID is a must (#588)

[w3c/payment-request] Be more explicit that only alphabetic codes are supported for currency codes (#585)

[w3c/payment-request] Be more explicit that only alphabetical codes are supported for currency codes (#585)

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

[w3c/payment-request] BREAKING CHANGE: change `supportedMethods` to DOMString (#551)

[w3c/payment-request] canMakePayment() needs to match .show() (#535)

[w3c/payment-request] Change around payment handler language proposed by AHB (#574)

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

[w3c/payment-request] Consider adding some means of getting the details out of a payment request (#592)

[w3c/payment-request] Considering allowing merchants to populate set of shipping addresses (#565)

[w3c/payment-request] Dealing with "other" payment methods (#580)

[w3c/payment-request] define PaymentRequest.shippingType attribute (#568)

[w3c/payment-request] Descriptions of change events attributes are somewhat misleading (#538)

[w3c/payment-request] details attribute is incorrect (#575)

[w3c/payment-request] Do not show payment requests for non-fully-active documents (#579)

[w3c/payment-request] Don't block UI if .updateWith() not called (closes #589) (#590)

[w3c/payment-request] Dont block UI if .updateWith() not called (closes #589) (#591)

[w3c/payment-request] Drop array support for supported methods? (#549)

[w3c/payment-request] Duplicate shippingOptions lead to inconsistent `updateWith()` - should throw! (#594)

[w3c/payment-request] editorial: add example of .toJSON()+fetch POST (#583)

[w3c/payment-request] Editorial: change around payment handler language (closes #532) (#574)

[w3c/payment-request] editorial: clarify currency member is alphabetic code (#587)

[w3c/payment-request] editorial: rewrite pay response details attr (#586)

[w3c/payment-request] editorial: s/Event/PaymentRequestUpdateEvent (closes #538) (#569)

[w3c/payment-request] Editorial: test annotations (#570)

[w3c/payment-request] Empty shippingOptions (ab)used as error (#595)

[w3c/payment-request] https://www.w3.org/TR/payment-request/#conditional-modifications-to-payment-request (#597)

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

[w3c/payment-request] l10n: adds Localizable dict + TextDirection enum (#455)

[w3c/payment-request] Matching algo doesn't handle absence of filters (#532)

[w3c/payment-request] Need short example of serializing response (#576)

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

[w3c/payment-request] PaymentItem.pending can be true, but transaction can "complete" (#571)

[w3c/payment-request] Real use case for .complete("unknown") - or mark "at risk" (#584)

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

[w3c/payment-request] remove matching .data text from .show() (#578)

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

[w3c/payment-request] Should PaymentItem.pending be marked "at risk"? (#571)

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

[w3c/payment-request] Support for "redirected" payment providers like PayPal, iDEAL/NL,Direktbetalning/SE etc (#573)

[w3c/payment-request] Third party Method not recognized- why (#593)

[w3c/payment-request] Throw on dup shippingOptions (closes #594, ##595) (#596)

[w3c/payment-request] Throw on dup shippingOptions ids (#596)

[w3c/payment-request] Throw on dup shippingOptions ids (closes #594, ##595) (#596)

[w3c/payment-request] Throw on dup shippingOptions ids (closes #594, #595) (#596)

[w3c/payment-request] Use first matching PaymentDetailsModifier (#541)

[w3c/payment-request] validate PaymentCurrencyAmount.currency (closes #490) (#567)

[w3c/payment-request] Validate PMIs, ignore duplicates (#581)

[w3c/payment-request] validate supportedMethods (#464)

[w3c/payment-request] What about billet payment option? (#577)

[w3c/webpayments-methods-tokenization] Should the response data include an "expires" field? (#12)

[w3c/webpayments-methods-tokenization] Structuring the tokenization payment method(s) (#13)

[w3c/webpayments-methods-tokenization] tokenProviderMerchantIdentifier vs merchantId (#18)

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

[w3c/webpayments-methods-tokenization] Wording of tokens used (#5)

Last message date: Thursday, 31 August 2017 23:28:20 UTC