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

[w3c/browser-payment-api] "contains a value for" isn't defined for dictionaries (#321)

[w3c/browser-payment-api] [WebIDL] reference is wrong (#394)

[w3c/browser-payment-api] `PaymentInstrument.complete(result)` wording (#402)

[w3c/browser-payment-api] A `PaymentItem` can't be a "valid decimal monetary value" (#334)

[w3c/browser-payment-api] A PaymentDetailsModifier may not have an additionalDisplayItems value present (#335)

[w3c/browser-payment-api] Add `enableLegacyCheckout` option to PaymentOptions. (#365)

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

[w3c/browser-payment-api] Add canMakePayment() method (#380)

[w3c/browser-payment-api] Ambiguous conformance requirement in constructor (#354)

[w3c/browser-payment-api] an event to providing standards for push payment methods (#223)

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

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

[w3c/browser-payment-api] Define [[waitForUpdate]] and make it clear where it lives (#407)

[w3c/browser-payment-api] DOMExceptions are now in WebIDL (#314)

[w3c/browser-payment-api] Drop redundant reference to secure context + other redefinitions (#399)

[w3c/browser-payment-api] Editorial: Add missing xrefs to various specs (#400)

[w3c/browser-payment-api] Editorial: don't capitalize RFC 2119 terms (#377)

[w3c/browser-payment-api] Editorial: firing an event is not done correctly (#401)

[w3c/browser-payment-api] Editorial: refer to methods with parentheses (closes #378) (#398)

[w3c/browser-payment-api] Editorial: refer to methods with parentheses for clarity, and spell out their params in their definition (#378)

[w3c/browser-payment-api] Editorial: use new language for DOMExceptions (#375)

[w3c/browser-payment-api] Editorial: use new language for DOMExceptions (close #375) (#397)

[w3c/browser-payment-api] Examples in the spec (#274)

[w3c/browser-payment-api] feat(payment resp algo): phone# SHOULD be E.164 (closes #390) (#396)

[w3c/browser-payment-api] fix(payment request algo): set attributes to null if not given (closes #385) (#391)

[w3c/browser-payment-api] Internal slots vs. attributes (#393)

[w3c/browser-payment-api] Invoke "allowed to use" always (#383)

[w3c/browser-payment-api] Is 'currencySystem' required? (#408)

[w3c/browser-payment-api] Is it intended that abort() rejects the acceptPromise and resolves its return value in separate tasks? (#340)

[w3c/browser-payment-api] Is section 3.4 informative or normative? (#342)

[w3c/browser-payment-api] Move state transitions diagram into a note (#406)

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

[w3c/browser-payment-api] PaymentDetails may not have values present for various sequences, but the PaymentRequest constructor assumes that it does (#333)

[w3c/browser-payment-api] PaymentRequest constructor validation ordering does not match Blink at all (#373)

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

[w3c/browser-payment-api] Phone number format (#390)

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

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

[w3c/browser-payment-api] Queue tasks to change developer-visible properties (#405)

[w3c/browser-payment-api] Remove confusing IDL comments (#395)

[w3c/browser-payment-api] Security hole in payment API when a constructor from a no longer active document is invoked (#361)

[w3c/browser-payment-api] Serializer behavior (#385)

[w3c/browser-payment-api] Setting internal slots of objects from asynchronous steps is not OK (#339)

[w3c/browser-payment-api] State how payment details modifier data is serialized and used (#404)

[w3c/browser-payment-api] Straighten out the payment method data flow (#382)

[w3c/browser-payment-api] style(index.html): cleanup markup (#392)

[w3c/browser-payment-api] The "data" member of PaymentDetailsModifier doesn't seem to be used for anything (#346)

[w3c/browser-payment-api] The "data" member of PaymentMethodData doesn't seem to actually be used for anything (#338)

[w3c/browser-payment-api] The myth of JSON-serializable object (#307)

[w3c/browser-payment-api] The shipping address/option changed algorithms should not be synchronously poking internal slots (#351)

[w3c/browser-payment-api] Various fixes to the PaymentRequest constructor (#374)

[w3c/browser-payment-api] waitForUpdate is not defined (#371)

[w3c/browser-payment-api] Why is the "shippingType" member of PaymentOptions not a PaymentShippingType? (#337)

[w3c/webpayments-method-identifiers] Changes to address Action #40 (#21)

[w3c/webpayments-method-identifiers] How should we address payment method manifest files? (#19)

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

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

[w3c/webpayments-methods-card] Fix typo stating BasicCardRequest as BasicCardResponse (#24)

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

[w3c/webpayments-payment-apps-api] (Deleted this edit by mistake before merged) (#78)

[w3c/webpayments-payment-apps-api] * updates around payment app registration, more clarity wrt user cons… (#93)

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

[w3c/webpayments-payment-apps-api] Add sentence on display of payment app origin (#100)

[w3c/webpayments-payment-apps-api] Clarification on Payment App "Options" (#90)

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

[w3c/webpayments-payment-apps-api] Edits based on recent discussions and decisions (#80)

[w3c/webpayments-payment-apps-api] Example 3 does not work (#82)

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

[w3c/webpayments-payment-apps-api] Introduce the PaymentAppResponseData dictionary (#84)

[w3c/webpayments-payment-apps-api] Lambda functions for app matching (#76)

[w3c/webpayments-payment-apps-api] Move secure context note from intro to where the requirement is listed. (#85)

[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] Payment App Decline (#92)

[w3c/webpayments-payment-apps-api] Payment app identifier to manifest filename mapping (#48)

[w3c/webpayments-payment-apps-api] payment-manifest.json and canHandle function (#83)

[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] Section 6 steps 1-5 seem to avoid selecting a payment option / payment method (#56)

[w3c/webpayments-payment-apps-api] Security note adjustment (#87)

[w3c/webpayments-payment-apps-api] security note moved (#86)

[w3c/webpayments-payment-apps-api] Should payment apps implement payment method-specific filters? (#63)

[w3c/webpayments-payment-apps-api] Should we allow payment providers to issue queries about their installed payment apps (match on origin) (#6)

[w3c/webpayments-payment-apps-api] Small fixes + displayItems (#88)

[w3c/webpayments-payment-apps-api] Split out enabled and supported methods (#7)

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

[w3c/webpayments-payment-apps-api] Updates around display of windows (#89)

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

[w3c/webpayments-payment-apps-api] Versioning (#45)

[w3c/webpayments-payment-apps-api] We need a PaymentAppResponseData dictionary (#81)

[w3c/webpayments-payment-apps-api] What is matching and display behavior for various scenarios of recommended apps, enabled apps, non-enabled apps, etc.? (#38)

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

Last message date: Tuesday, 31 January 2017 23:51:40 UTC