public-webpayments-specs@w3.org from September 2016 by subject

[w3c/browser-payment-api] "Incognito mode" notes (#238)

[w3c/browser-payment-api] Add allowpaymentrequest attribute for iframe support (#268)

[w3c/browser-payment-api] Add error message that can be provided as part of updateWith (#257)

[w3c/browser-payment-api] Add Guidance Text for Incognito Mode (#230)

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

[w3c/browser-payment-api] Add informative reference to CLDR (#277)

[w3c/browser-payment-api] Add note preferring GitHub issues over e-mail. (#245)

[w3c/browser-payment-api] Add security text regarding payment apps and phishing (#233)

[w3c/browser-payment-api] Add support for currency system. (#267)

[w3c/browser-payment-api] Added clarification about target of details (#282)

[w3c/browser-payment-api] Annotate all interfaces with SecureContext (#241)

[w3c/browser-payment-api] API flow (#177)

[w3c/browser-payment-api] Can the merchant influence order of presentation of payment apps to the user (#23)

[w3c/browser-payment-api] Cannot use 2119 terms in notes (#240)

[w3c/browser-payment-api] Clarify that HTTPS is required to use the API (#232)

[w3c/browser-payment-api] Create failure-handling.md (#248)

[w3c/browser-payment-api] Currency Types and Rendering (#185)

[w3c/browser-payment-api] Decorate all interfaces with [SecureContext] (#251)

[w3c/browser-payment-api] Describe risk of exposing available payment methods (#284)

[w3c/browser-payment-api] Detecting payment method support (#247)

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

[w3c/browser-payment-api] Ensure references are up-to-date (#20)

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

[w3c/browser-payment-api] Expand Privacy Considerations Section (#228)

[w3c/browser-payment-api] Expand Security Considerations Section (#231)

[w3c/browser-payment-api] Fix shippingType to avoid TypeError (#285)

[w3c/browser-payment-api] Fix two minor typos. (#220)

[w3c/browser-payment-api] Fix typo in PaymentItem definition (#255)

[w3c/browser-payment-api] Fixed a typo (#276)

[w3c/browser-payment-api] Fixed typos (#281)

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

[w3c/browser-payment-api] If a card payment fails, should we support exclusion of that card instrument from matching? (#237)

[w3c/browser-payment-api] Ignore shipping options if there are duplicate IDs. (#249)

[w3c/browser-payment-api] Implementations may choose to implement a timeouts (#253)

[w3c/browser-payment-api] ISO4217 is informative. (#250)

[w3c/browser-payment-api] Make ISO4217 an informative reference rather than normative (#242)

[w3c/browser-payment-api] Make response serializable. (#252)

[w3c/browser-payment-api] Make text active voice, present tense (#272)

[w3c/browser-payment-api] Make UAs throw for invalid monetary amounts (#256)

[w3c/browser-payment-api] Normative References (#227)

[w3c/browser-payment-api] notifying the payment app when a payment is complete (#286)

[w3c/browser-payment-api] Payment app discovery (#155)

[w3c/browser-payment-api] Payment Instrument clarification (#104)

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

[w3c/browser-payment-api] PaymentRequest constructor errors should be properly annotated (#290)

[w3c/browser-payment-api] PR #259 and #262 updated the references (#263)

[w3c/browser-payment-api] Propose a payment method specification that includes an example of field level security (#141)

[w3c/browser-payment-api] Reducing the gap to Apple's API (#270)

[w3c/browser-payment-api] Remove careOf field and add note to recipient field. (#258)

[w3c/browser-payment-api] Remove explanation using "parties" (#266)

[w3c/browser-payment-api] Remove issue markers for issues postponed past v1. (#269)

[w3c/browser-payment-api] Remove must in complete() (#280)

[w3c/browser-payment-api] Remove restriction that payment method identifier only appear once (#261)

[w3c/browser-payment-api] Remove the dependency on PAYMENT-ARCH. (#262)

[w3c/browser-payment-api] Request to remove 'careOf' field from the PaymentAddress interface (#244)

[w3c/browser-payment-api] Should show() depend on a user action? (#283)

[w3c/browser-payment-api] Should the API support field validation? (#225)

[w3c/browser-payment-api] Should the payment mediator pass all payment method data to the payment app or just relevant data? (#157)

[w3c/browser-payment-api] Should the Payment Request API only be available in a top-level browsing context? (#2)

[w3c/browser-payment-api] Specify UA requirements if “id” field of PaymentShippingOption is not unique (#243)

[w3c/browser-payment-api] Specify UA requirements if “value” field of PaymentCurrencyAmount does not match syntax requirements (#260)

[w3c/browser-payment-api] There might be a conflict between 'shippingType' in PaymentOptions and WebIDL binding. (#271)

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

[w3c/browser-payment-api] Tidied up text in notes. (#254)

[w3c/browser-payment-api] Unambiguously specify UA requirements for instances that are not valid (#235)

[w3c/browser-payment-api] Update editor list (#288)

[w3c/browser-payment-api] Update Introduction to describe actors better (#121)

[w3c/browser-payment-api] Update references to "Payment Transaction Message Specification" (#218)

[w3c/browser-payment-api] Update Respec config. (#246)

[w3c/browser-payment-api] Update the issues links to exclude postponed issues that we don't pla… (#264)

[w3c/browser-payment-api] Updated WebIDL and Secure Contexts references (#259)

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

[w3c/browser-payment-api] What if the user refuses to supply a shipping address (#279)

[w3c/browser-payment-api] What should happen when invalid data is provided? (#265)

[w3c/webpayments-method-identifiers] Add github links (#14)

[w3c/webpayments-method-identifiers] Identifier equivalence does not handle failure (#8)

[w3c/webpayments-method-identifiers] Schema.org PaymentMethod as namespace for short strings (#13)

[w3c/webpayments-method-identifiers] Update editor list (#15)

[w3c/webpayments-method-identifiers] Why URLs? (#9)

[w3c/webpayments-methods-card] Add Security Considerations and Privacy Considerations sections (#6)

[w3c/webpayments-methods-card] Added BasicCardRequest dictionary supporting specification of RequiredFields (#4)

[w3c/webpayments-methods-card] Describe the payment method request data. (#13)

[w3c/webpayments-methods-card] Editorial suggestions (#9)

[w3c/webpayments-methods-card] Reference trademarks (#1)

[w3c/webpayments-methods-card] Remove flow diagram. (#14)

[w3c/webpayments-methods-card] Remove PAYMENT-ARCH dependency and update links to new repo (#10)

[w3c/webpayments-methods-card] Storing card information (#2)

[w3c/webpayments-methods-card] Update editor list (#15)

[w3c/webpayments-methods-card] Update references and issue markers (#3)

[w3c/webpayments-methods-card] Update the payment method identifier to "basic-card" (#12)

[w3c/webpayments-methods-card] Update to use the PaymentAddress type for billing address. (#11)

[w3c/webpayments-payment-apps-api] add parens for clause (#58)

[w3c/webpayments-payment-apps-api] Added optionId field to PaymentAppRequestData dictionary (#44)

[w3c/webpayments-payment-apps-api] change 'promise' to 'Promise' (#57)

[w3c/webpayments-payment-apps-api] Cleaned up text (#52)

[w3c/webpayments-payment-apps-api] Cleanup wording (#55)

[w3c/webpayments-payment-apps-api] Editorial fixes (#42)

[w3c/webpayments-payment-apps-api] Editorial tweaks after Rouslan edits (#62)

[w3c/webpayments-payment-apps-api] Extending invocation of payment apps with other techniques than HTTP (#10)

[w3c/webpayments-payment-apps-api] Fix run-on sentence (#54)

[w3c/webpayments-payment-apps-api] Fixed duplicate wording (#61)

[w3c/webpayments-payment-apps-api] Fixed grammar (#53)

[w3c/webpayments-payment-apps-api] How can a Browser-based Payment App cancel the payment flow? (#37)

[w3c/webpayments-payment-apps-api] How can a Web Based Payment App cancel the payment flow? (#37)

[w3c/webpayments-payment-apps-api] How is registration information updated? (#36)

[w3c/webpayments-payment-apps-api] Implications from non registration (via AHB) (#40)

[w3c/webpayments-payment-apps-api] Links to terms and common terminology (#50)

[w3c/webpayments-payment-apps-api] Native payment app support and others changes. (#46)

[w3c/webpayments-payment-apps-api] Numerous changes based on Rouslan review and issue migration (#39)

[w3c/webpayments-payment-apps-api] Pass along a Transaction ID (#47)

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

[w3c/webpayments-payment-apps-api] Payment apps and methods, are they the same? (#35)

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

[w3c/webpayments-payment-apps-api] Proposed text for service-worker-based implementation of payment apps (#41)

[w3c/webpayments-payment-apps-api] Remove duplicate item (#60)

[w3c/webpayments-payment-apps-api] Removed <a> until I figure out how to get rid of entry from imported glossary (#43)

[w3c/webpayments-payment-apps-api] Require secure contexts for web-based payment apps (#24)

[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] Should payment instrument details be included at registration? (#12)

[w3c/webpayments-payment-apps-api] Should the browser pass user data it has collected (email etc) to the payment app? (#13)

[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] Should we distinguish the identifier for a payment app from the identifier for the app server that processes payments? (#20)

[w3c/webpayments-payment-apps-api] The relationship between payment apps and service workers (#33)

[w3c/webpayments-payment-apps-api] Thoughts on the current spec (#34)

[w3c/webpayments-payment-apps-api] Use 'user agent' all the time (#51)

[w3c/webpayments-payment-apps-api] Users MUST be able to prevent the display of unregistered payment apps (#59)

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

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

[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] What is the process for rendering the payment app UI (#4)

[w3c/webpayments-payment-apps-api] “Security Error” on different origins (#9)

Last message date: Thursday, 29 September 2016 15:22:51 UTC