public-webpayments-specs@w3.org from June 2016 by date

Wednesday, 29 June 2016

Re: [w3c/browser-payment-api] Should the Payment Request API only be available in a top-level browsing context? (#2) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Should the Payment Request API only be available in a top-level browsing context? (#2) Zach Koch

Tuesday, 28 June 2016

[w3c/browser-payment-api] Fix a minor typo in PaymentRequest constructor description. (#221) Jinho Bang
Re: [w3c/browser-payment-api] Should the Payment Request API only be available in a top-level browsing context? (#2) Michael[tm] Smith

Monday, 27 June 2016

Saturday, 25 June 2016

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

Friday, 24 June 2016

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

Thursday, 23 June 2016

Re: [w3c/browser-payment-api] Currency Types and Rendering (#185) ianbjacobs
Re: [w3c/browser-payment-api] Currency Types and Rendering (#185) adamroach
Re: [w3c/browser-payment-api] Currency Types and Rendering (#185) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Currency Types and Rendering (#185) adamroach
Re: [w3c/browser-payment-api] Currency Types and Rendering (#185) adamroach
Re: [w3c/browser-payment-api] Currency Types and Rendering (#185) Manu Sporny
Re: [w3c/browser-payment-api] Support for gift cards and discount codes (#145) Ajay Kapur

Wednesday, 22 June 2016

Re: [w3c/browser-payment-api] Currency Types and Rendering (#185) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Currency Types and Rendering (#185) ianbjacobs
Re: [w3c/browser-payment-api] Currency Types and Rendering (#185) Manu Sporny
Re: [w3c/browser-payment-api] Currency Types and Rendering (#185) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Currency Types and Rendering (#185) ianbjacobs
Re: [w3c/browser-payment-api] Currency Types and Rendering (#185) Adrian Hope-Bailie
Re: [w3c/webpayments-method-identifiers] Should we define nesting/grouping semantics for payment method identifier matching? (#1) ianbjacobs
Re: [w3c/webpayments-method-identifiers] Should we define nesting/grouping semantics for payment method identifier matching? (#1) Rouslan Solomakhin
Re: [w3c/webpayments-method-identifiers] Should we define nesting/grouping semantics for payment method identifier matching? (#1) ianbjacobs
Re: [w3c/webpayments-method-identifiers] Should we define nesting/grouping semantics for payment method identifier matching? (#1) Rouslan Solomakhin
Re: [w3c/browser-payment-api] Currency Types and Rendering (#185) ianbjacobs
Re: [w3c/browser-payment-api] Update Introduction to describe actors better (#121) Rouslan Solomakhin
Re: [w3c/browser-payment-api] Propose a payment method specification that includes an example of field level security (#141) Rouslan Solomakhin
Re: [w3c/browser-payment-api] Currency Types and Rendering (#185) Rouslan Solomakhin

Tuesday, 21 June 2016

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

Monday, 20 June 2016

Re: [w3c/browser-payment-api] How will the spec address versioning / feature detection? (#33) adamroach
Re: [w3c/browser-payment-api] How will the spec address versioning / feature detection? (#33) adamroach
Re: [w3c/browser-payment-api] How will the spec address versioning / feature detection? (#33) Ade Bateman
Re: [w3c/browser-payment-api] How will the spec address versioning / feature detection? (#33) adamroach
Re: [w3c/browser-payment-api] How will the spec address versioning / feature detection? (#33) Manu Sporny
Re: [w3c/browser-payment-api] How will the spec address versioning / feature detection? (#33) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] How will the spec address versioning / feature detection? (#33) Ade Bateman
Re: [w3c/webpayments-methods-card] Added BasicCardRequest dictionary supporting specification of RequiredFields (#4) mattsaxon
Re: [w3c/browser-payment-api] How will the spec address versioning / feature detection? (#33) Rouslan Solomakhin
Re: [w3c/browser-payment-api] Specifying Mandatory Data (#97) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] How will the spec address versioning / feature detection? (#33) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] How are web-based payment apps supported? (#39) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Add section on Extensibility (#44) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Combine API parameters into a single request object + options (#15) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Merge Payment Request Architecture with Capabilities Document (#42) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Any plan to allow this API to be called by non-merchants? (#35) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Add section on internationalization (#53) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Should show() be renamed? (#127) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Is it neccessary to distinguish the origin of data provided in the payment response, and how would we do it? (#173) Adrian Hope-Bailie

Saturday, 18 June 2016

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

Friday, 17 June 2016

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

Thursday, 16 June 2016

Wednesday, 15 June 2016

Re: [w3c/browser-payment-api] Any plan to allow this API to be called by non-merchants? (#35) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Should payment app registration be included in the conformance criteria of the browser API spec? (#8) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Should payment app registration be included in the conformance criteria of the browser API spec? (#8) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Any plan to allow this API to be called by non-merchants? (#35) Dave Longley
Re: [w3c/browser-payment-api] How are payment requests and responses passed between the browser and third-party native wallets? (#50) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] How are payment requests and responses passed between the browser and third-party native wallets? (#50) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] How are web-based payment apps supported? (#39) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] How are web-based payment apps supported? (#39) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Specifying Mandatory Data (#97) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Payment Instrument clarification (#104) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] What is the extensibility mechanism for the payment request and response messages? (#146) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] What is the extensibility mechanism for the payment request and response messages? (#146) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Should payment app registration be included in the conformance criteria of the browser API spec? (#8) Tri Nguyen
Re: [w3c/browser-payment-api] Add section on Extensibility (#44) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Add section on Extensibility (#44) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Write-up initial proposal for payment app registration spec (#12) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Write-up initial proposal for payment app registration spec (#12) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Should the browser pass user data it has collected (email etc) to the payment app? (#194) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Should the browser pass user data it has collected (email etc) to the payment app? (#194) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Should payment app registration be included in the conformance criteria of the browser API spec? (#8) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Should payment app registration be included in the conformance criteria of the browser API spec? (#8) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Combine API parameters into a single request object + options (#15) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] How will the spec address versioning / feature detection? (#33) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Any plan to allow this API to be called by non-merchants? (#35) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Any plan to allow this API to be called by non-merchants? (#35) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Merge Payment Request Architecture with Capabilities Document (#42) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Should Payment Method Identifiers and Messages be expressed using a Linked Data Vocabulary? (#45) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Should the payment API be more conversational or less conversational? (#51) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Should the payment API be more conversational or less conversational? (#51) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Add section on internationalization (#53) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] What component does the payment method intersection? (#103) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] What component does the payment method intersection? (#103) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Should we standardise a callback mechanism for payment apps to communicate to 3rd parties? (#109) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Should we standardise a callback mechanism for payment apps to communicate to 3rd parties? (#109) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Should show() be renamed? (#127) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Is it neccessary to distinguish the origin of data provided in the payment response, and how would we do it? (#173) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Dynamic Currency Conversion (DCC) Support (#178) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Update "user accepts the payment request algorithm" to include interaction with payment app (#192) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Update "user accepts the payment request algorithm" to include interaction with payment app (#192) Adrian Hope-Bailie
[w3c/browser-payment-api] Update references to "Payment Transaction Message Specification" (#218) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Add shippingOption to response (#217) Ade Bateman
Re: [w3c/browser-payment-api] What about billing address (#216) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] What about billing address (#216) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Add shippingOption to response (#217) Rouslan Solomakhin
[w3c/browser-payment-api] Add shippingOption to response (#217) Ade Bateman
Re: [w3c/browser-payment-api] Update promise rejection (#187) Ade Bateman
Re: [w3c/browser-payment-api] Update promise rejection (#187) Ade Bateman
Re: [w3c/browser-payment-api] Should it be possible to vary amounts depending on payment method (#4) Ade Bateman
Re: [w3c/browser-payment-api] Should it be possible to vary amounts depending on payment method (#4) Ade Bateman
Re: [w3c/browser-payment-api] Remove unnecessary clause about validation. (#213) Ade Bateman
Re: [w3c/browser-payment-api] Spec prohibits currency validation but doesn't define what it is (#175) Ade Bateman
Re: [w3c/browser-payment-api] What about billing address (#216) ianbjacobs
[w3c/browser-payment-api] What about billing address (#216) Barış Güler

Monday, 13 June 2016

Friday, 10 June 2016

Thursday, 9 June 2016

Wednesday, 8 June 2016

Re: [w3c/browser-payment-api] Should we support a delegated state for PaymentRequest? (#7) Ade Bateman
Re: [w3c/browser-payment-api] Should we support a delegated state for PaymentRequest? (#7) Ade Bateman
Re: [w3c/browser-payment-api] Support different amounts per payment method. (#211) Ade Bateman
[w3c/browser-payment-api] Remove unnecessary clause about validation. (#213) Ade Bateman
Re: [w3c/browser-payment-api] Simple editorial fixes. (#212) Ade Bateman
[w3c/browser-payment-api] Simple editorial fixes. (#212) Ade Bateman
Re: [w3c/browser-payment-api] Proposal to abort if updateWith promise is rejected (#209) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Remove special case handling for single shipping option. (#210) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Support different amounts per payment method. (#211) Rouslan Solomakhin
Re: [w3c/browser-payment-api] Support different amounts per payment method. (#211) ianbjacobs
Re: [w3c/browser-payment-api] Support different amounts per payment method. (#211) Dave Longley
Re: [w3c/browser-payment-api] Support different amounts per payment method. (#211) ianbjacobs
Re: [w3c/browser-payment-api] Proposal to abort if updateWith promise is rejected (#209) Rouslan Solomakhin
Re: [w3c/browser-payment-api] Remove special case handling for single shipping option. (#210) ianbjacobs
Re: [w3c/browser-payment-api] Remove special case handling for single shipping option. (#210) Rouslan Solomakhin
Re: [w3c/browser-payment-api] Support different amounts per payment method. (#211) Rouslan Solomakhin
[w3c/browser-payment-api] Support different amounts per payment method. (#211) Ade Bateman
[w3c/browser-payment-api] Remove special case handling for single shipping option. (#210) Ade Bateman
Re: [w3c/browser-payment-api] Update "user accepts the payment request algorithm" to include interaction with payment app (#192) Ade Bateman
[w3c/browser-payment-api] Proposal to abort if updateWith promise is rejected (#209) Ade Bateman
Re: [w3c/browser-payment-api] Rename remaining types so that all begin Payment* (#208) Ade Bateman

Tuesday, 7 June 2016

Re: [w3c/browser-payment-api] Move PMI and Card specs out of repo (#207) Ade Bateman

Friday, 3 June 2016

Re: [w3c/browser-payment-api] Terms and conditions next to "Pay" button (#195) Rouslan Solomakhin
Re: [w3c/browser-payment-api] Terms and conditions next to "Pay" button (#195) Rouslan Solomakhin

Thursday, 2 June 2016

Re: [w3c/browser-payment-api] Rename remaining types so that all begin Payment* (#208) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Currency Types and Rendering (#185) Adrian Hope-Bailie

Wednesday, 1 June 2016

[w3c/browser-payment-api] Rename remaining types so that all begin Payment* (#208) Ade Bateman
Re: [w3c/browser-payment-api] Currency Types and Rendering (#185) Rouslan Solomakhin
Re: [w3c/browser-payment-api] Update promise rejection (#187) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Update promise rejection (#187) adamroach
Re: [w3c/browser-payment-api] Currency Types and Rendering (#185) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Update promise rejection (#187) Adrian Hope-Bailie

Last message date: Wednesday, 29 June 2016 12:03:56 UTC