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

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

[w3c/browser-payment-api] `country` vs `sortingCode` (#434)

[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] Addition of flag on PaymentMethodData to indicate that line items should be shared with apps (#446)

[w3c/browser-payment-api] Authors are not conformance classes (#440)

[w3c/browser-payment-api] BREAKING CHANGE: s/paymentRequestID/paymentRequestId (closes #414) (#419)

[w3c/browser-payment-api] Collect Privacy and Security considerations (#331)

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

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

[w3c/browser-payment-api] DOMStrings don't contain "characters" (#322)

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

[w3c/browser-payment-api] Dynamic Currency Conversion requirements (#289)

[w3c/browser-payment-api] Editorial fixes and xrefs (#422)

[w3c/browser-payment-api] editorial(intro): drop hyperbolic statements (closes #410) (#411)

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

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

[w3c/browser-payment-api] Editorial: define and link to the different states (#376)

[w3c/browser-payment-api] editorial: dfn payment request states as strings (closes #376) (#429)

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

[w3c/browser-payment-api] editorial: don't redefine WebIDL things (closes #399) (#430)

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

[w3c/browser-payment-api] editorial: fix linking to DOM spec (#423)

[w3c/browser-payment-api] editorial: fix linking to various specs (#423)

[w3c/browser-payment-api] editorial: s/character/code point/ (closes #322) (#421)

[w3c/browser-payment-api] editorial: s/character/code unit/ (closes #322) (#421)

[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] feat: put request id in details dictionary (#426)

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

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

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

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

[w3c/browser-payment-api] fix: IDL dictates what is/isn't required (closes #408) (#431)

[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 are currency systems expected to be implemented in practice? (#343)

[w3c/browser-payment-api] How are digital signatures supported for Payment Requests? (#291)

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

[w3c/browser-payment-api] Introduction is aspirational, but misleading (#410)

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

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

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

[w3c/browser-payment-api] Making this API work with HTML Forms (#330)

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

[w3c/browser-payment-api] PaymentAddress should be a dictionary (#299)

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

[w3c/browser-payment-api] PaymentOptions seems overly verbose/overlaps with HTML (#326)

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

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

[w3c/browser-payment-api] paymentRequestID is spelled wrong :( (#414)

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

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

[w3c/browser-payment-api] RCF2119 keywords in informative sections (#439)

[w3c/browser-payment-api] Response/Request semantics and cancellation (#298)

[w3c/browser-payment-api] Set all the attributes of PaymentResponse when creating it (#417)

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

[w3c/browser-payment-api] Take paymentRequestID in constructor (#413)

[w3c/browser-payment-api] Throwing exceptions rather than permitting broken usage (#275)

[w3c/browser-payment-api] Update the shippingType option to not allow invalid strings (#416)

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

[w3c/browser-payment-api] Web page and developer (#437)

[w3c/browser-payment-api] What is the mechanism for limiting repeated calls to canMakePayments ? (#367)

[w3c/browser-payment-api] What is the shippingAddress/shippingOption of a PaymentResponse if requestShipping was false? (#352)

[w3c/browser-payment-api] Why is details.total.amount.value not a number? (#301)

[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] Circular dependency between PMI and PR specs (#22)

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

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

[w3c/webpayments-method-identifiers] slight rewording (#6)

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

[w3c/webpayments-method-identifiers] Support for PMI's with schemes other than https? (#17)

[w3c/webpayments-method-identifiers] update pmi spec with apen and proprietary payment method identifiers (#10)

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

[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] Don't send display items to payment handler (#103)

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

[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 identifier to manifest filename mapping (#48)

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

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

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

[w3c/webpayments-payment-apps-api] Recovery of a failed Push Payment (#102)

[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] Simplify Example 3 as per issue #82 (#101)

[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: Tuesday, 28 February 2017 19:49:15 UTC