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

Tuesday, 31 January 2017

• Re: [w3c/webpayments-payment-apps-api] Revisiting payment app filtering (#96) Marcos Cáceres
• Re: [w3c/browser-payment-api] Add billing shipping type (#409) rvm4
• Re: [w3c/webpayments-payment-apps-api] Revisiting payment app filtering (#96) Adrian Hope-Bailie
• Re: [w3c/webpayments-payment-apps-api] Revisiting payment app filtering (#96) adamroach
• Re: [w3c/webpayments-payment-apps-api] Payment app identifier to manifest filename mapping (#48) Tommy Thorsen
• Re: [w3c/webpayments-payment-apps-api] Revisiting payment app filtering (#96) Rouslan Solomakhin
• Re: [w3c/webpayments-payment-apps-api] Multiple payment apps per origin (#98) Dave Longley
• Re: [w3c/webpayments-payment-apps-api] Multiple payment apps per origin (#98) Adrian Hope-Bailie
• Re: [w3c/webpayments-payment-apps-api] Revisiting payment app filtering (#96) Adrian Hope-Bailie
• Re: [w3c/webpayments-payment-apps-api] Revisiting payment app filtering (#96) Jake Archibald
• Re: [w3c/webpayments-payment-apps-api] Revisiting payment app filtering (#96) Rouslan Solomakhin
• Re: [w3c/webpayments-payment-apps-api] Revisiting payment app filtering (#96) Rouslan Solomakhin
• Re: [w3c/webpayments-payment-apps-api] Revisiting payment app filtering (#96) adamroach
• Re: [w3c/webpayments-payment-apps-api] Multiple payment apps per origin (#98) Dave Longley
• Re: [w3c/webpayments-payment-apps-api] Payment app identifier to manifest filename mapping (#48) Jake Archibald
• Re: [w3c/webpayments-payment-apps-api] Use PaymentRequest and PaymentResponse (#99) Dave Longley
• Re: [w3c/webpayments-payment-apps-api] Revisiting payment app filtering (#96) adamroach
• Re: [w3c/webpayments-payment-apps-api] Revisiting payment app filtering (#96) Adrian Hope-Bailie
• Re: [w3c/webpayments-payment-apps-api] Multiple payment apps per origin (#98) Adrian Hope-Bailie
• Re: [w3c/webpayments-payment-apps-api] Payment app identifier to manifest filename mapping (#48) Tommy Thorsen
• Re: [w3c/webpayments-payment-apps-api] Revisiting payment app filtering (#96) Marcos Cáceres
• Re: [w3c/webpayments-payment-apps-api] Need to specify behavior for Clients.openWindow (#73) Marcos Cáceres
• Re: [w3c/webpayments-payment-apps-api] Use PaymentRequest and PaymentResponse (#99) Marcos Cáceres
• Re: [w3c/webpayments-payment-apps-api] Use PaymentRequest and PaymentResponse (#99) Marcos Cáceres
• Re: [w3c/webpayments-payment-apps-api] Use PaymentRequest and PaymentResponse (#99) Dave Longley
• Re: [w3c/webpayments-payment-apps-api] Use PaymentRequest and PaymentResponse (#99) Marcos Cáceres
• Re: [w3c/webpayments-payment-apps-api] Use PaymentRequest and PaymentResponse (#99) Marcos Cáceres
• Re: [w3c/webpayments-payment-apps-api] Use PaymentRequest and PaymentResponse (#99) adamroach
• Re: [w3c/webpayments-payment-apps-api] Use PaymentRequest and PaymentResponse (#99) Marcos Cáceres
• Re: [w3c/webpayments-payment-apps-api] Use PaymentRequest and PaymentResponse (#99) Marcos Cáceres
• Re: [w3c/webpayments-payment-apps-api] Use PaymentRequest and PaymentResponse (#99) Marcos Cáceres
• Re: [w3c/webpayments-payment-apps-api] Use PaymentRequest and PaymentResponse (#99) Marcos Cáceres

Monday, 30 January 2017

• Re: [w3c/webpayments-payment-apps-api] Use PaymentRequest and PaymentResponse (#99) adamroach
• Re: [w3c/webpayments-payment-apps-api] Payment App Decline (#92) ianbjacobs
• Re: [w3c/webpayments-payment-apps-api] Payment App Decline (#92) ianbjacobs
• Re: [w3c/webpayments-payment-apps-api] Payment app identifier to manifest filename mapping (#48) Jake Archibald
• Re: [w3c/browser-payment-api] Is 'currencySystem' required? (#408) Marcos Cáceres
• Re: [w3c/browser-payment-api] Move state transitions diagram into a note (#406) Marcos Cáceres
• Re: [w3c/browser-payment-api] Is section 3.4 informative or normative? (#342) Marcos Cáceres
• Re: [w3c/browser-payment-api] Move state transitions diagram into a note (#406) Marcos Cáceres
• Re: [w3c/webpayments-methods-card] Say how we integrate with PaymentRequest (#23) Marcos Cáceres
• Re: [w3c/webpayments-payment-apps-api] Example 3 does not work (#82) Marcos Cáceres
• Re: [w3c/webpayments-payment-apps-api] Example 3 does not work (#82) Marcos Cáceres
• Re: [w3c/browser-payment-api] Providing/Generating paymentRequestID during construction (#388) Marcos Cáceres

Saturday, 28 January 2017

• Re: [w3c/webpayments-payment-apps-api] Use PaymentRequest and PaymentResponse (#99) Salvador de la Puente González
• Re: [w3c/webpayments-payment-apps-api] Multiple payment apps per origin (#98) Salvador de la Puente González

Friday, 27 January 2017

• Re: [w3c/webpayments-payment-apps-api] Multiple payment apps per origin (#98) Dave Longley
• Re: [w3c/webpayments-payment-apps-api] Multiple payment apps per origin (#98) Dave Longley
• Re: [w3c/browser-payment-api] Add billing shipping type (#409) Dave Longley
• Re: [w3c/browser-payment-api] Add billing shipping type (#409) Dave Longley
• Re: [w3c/webpayments-payment-apps-api] Revisiting payment app filtering (#96) Marcos Cáceres
• Re: [w3c/webpayments-payment-apps-api] Revisiting payment app filtering (#96) Adrian Hope-Bailie
• Re: [w3c/webpayments-payment-apps-api] Payment app identifier to manifest filename mapping (#48) Tommy Thorsen
• Re: [w3c/webpayments-payment-apps-api] Add explicit permission call to allow payment app to handle payments (#94) Marcos Cáceres
• Re: [w3c/webpayments-payment-apps-api] Add explicit permission call to allow payment app to handle payments (#94) Marcos Cáceres
• Re: [w3c/webpayments-payment-apps-api] Multiple payment apps per origin (#98) Marcos Cáceres
• Re: [w3c/webpayments-payment-apps-api] Multiple payment apps per origin (#98) ianbjacobs
• Re: [w3c/webpayments-payment-apps-api] Multiple payment apps per origin (#98) Marcos Cáceres
• Re: [w3c/webpayments-payment-apps-api] Multiple payment apps per origin (#98) ianbjacobs
• Re: [w3c/webpayments-payment-apps-api] Multiple payment apps per origin (#98) Marcos Cáceres
• Re: [w3c/webpayments-payment-apps-api] Multiple payment apps per origin (#98) ianbjacobs
• Re: [w3c/webpayments-payment-apps-api] Multiple payment apps per origin (#98) Marcos Cáceres
• Re: [w3c/browser-payment-api] Add billing shipping type (#409) Marcos Cáceres

Thursday, 26 January 2017

• Re: [w3c/browser-payment-api] Add billing shipping type (#409) Rouslan Solomakhin
• Re: [w3c/browser-payment-api] Add billing shipping type (#409) ianbjacobs
• Re: [w3c/browser-payment-api] Add billing shipping type (#409) rvm4
• Re: [w3c/browser-payment-api] Add billing shipping type (#409) Rouslan Solomakhin
• Re: [w3c/webpayments-payment-apps-api] Revisiting payment app filtering (#96) adamroach
• Re: [w3c/webpayments-payment-apps-api] Revisiting payment app filtering (#96) Jake Archibald
• Re: [w3c/browser-payment-api] Add billing shipping type (#409) rvm4
• Re: [w3c/browser-payment-api] Add billing shipping type (#409) rvm4
• Re: [w3c/browser-payment-api] Add billing shipping type (#409) Domenic Denicola
• [w3c/browser-payment-api] Add billing shipping type (#409) rvm4
• Re: [w3c/webpayments-payment-apps-api] Revisiting payment app filtering (#96) adamroach
• Re: [w3c/webpayments-payment-apps-api] Revisiting payment app filtering (#96) adamroach
• Re: [w3c/webpayments-payment-apps-api] Revisiting payment app filtering (#96) Jake Archibald
• Re: [w3c/webpayments-payment-apps-api] Revisiting payment app filtering (#96) adamroach
• [w3c/webpayments-method-identifiers] Changes to address Action #40 (#21) Adrian Hope-Bailie
• Re: [w3c/webpayments-payment-apps-api] Payment app identifier to manifest filename mapping (#48) ianbjacobs
• Re: [w3c/webpayments-payment-apps-api] Revisiting payment app filtering (#96) Jake Archibald
• Re: [w3c/webpayments-payment-apps-api] Revisiting payment app filtering (#96) Tommy Thorsen
• Re: [w3c/webpayments-payment-apps-api] Payment app identifier to manifest filename mapping (#48) Tommy Thorsen

Wednesday, 25 January 2017

• Re: [w3c/browser-payment-api] The myth of JSON-serializable object (#307) Marcos Cáceres
• Re: [w3c/browser-payment-api] The "data" member of PaymentDetailsModifier doesn't seem to be used for anything (#346) Marcos Cáceres
• Re: [w3c/browser-payment-api] State how payment details modifier data is serialized and used (#404) Marcos Cáceres
• Re: [w3c/webpayments-payment-apps-api] Revisiting payment app filtering (#96) Tommy Thorsen
• Re: [w3c/webpayments-payment-apps-api] Multiple payment apps per origin (#98) Conor Hackett
• Re: [w3c/webpayments-payment-apps-api] Multiple payment apps per origin (#98) adamroach
• Re: [w3c/webpayments-payment-apps-api] Multiple payment apps per origin (#98) adamroach
• Re: [w3c/webpayments-payment-apps-api] Multiple payment apps per origin (#98) Marcos Cáceres
• Re: [w3c/webpayments-payment-apps-api] Multiple payment apps per origin (#98) Jake Archibald
• Re: [w3c/webpayments-payment-apps-api] Multiple payment apps per origin (#98) Marcos Cáceres
• Re: [w3c/webpayments-payment-apps-api] Need to specify behavior for Clients.openWindow (#73) Jenan Wise
• Re: [w3c/webpayments-payment-apps-api] Revisiting payment app filtering (#96) Jake Archibald
• Re: [w3c/webpayments-payment-apps-api] Revisiting payment app filtering (#96) adamroach
• Re: [w3c/webpayments-payment-apps-api] Revisiting payment app filtering (#96) Tommy Thorsen
• Re: [w3c/webpayments-payment-apps-api] Multiple payment apps per origin (#98) Jake Archibald
• Re: [w3c/webpayments-payment-apps-api] Multiple payment apps per origin (#98) ianbjacobs
• Re: [w3c/webpayments-payment-apps-api] Revisiting payment app filtering (#96) Jake Archibald
• Re: [w3c/webpayments-payment-apps-api] Revisiting payment app filtering (#96) Tommy Thorsen
• Re: [w3c/webpayments-payment-apps-api] Revisiting payment app filtering (#96) Marcos Cáceres
• Re: [w3c/webpayments-payment-apps-api] Revisiting payment app filtering (#96) Tommy Thorsen
• Re: [w3c/webpayments-payment-apps-api] Use PaymentRequest and PaymentResponse (#99) Marcos Cáceres
• Re: [w3c/webpayments-payment-apps-api] Revisiting payment app filtering (#96) Marcos Cáceres
• Re: [w3c/webpayments-payment-apps-api] Revisiting payment app filtering (#96) Tommy Thorsen
• Re: [w3c/webpayments-payment-apps-api] Replace setManifest()/getManifest() with set()/get()/keys()/has()/delete() (#95) Adrian Hope-Bailie
• Re: [w3c/webpayments-payment-apps-api] Revisiting payment app filtering (#96) Adrian Hope-Bailie
• Re: [w3c/webpayments-payment-apps-api] Use PaymentRequest and PaymentResponse (#99) Adrian Hope-Bailie
• Re: [w3c/webpayments-payment-apps-api] Multiple payment apps per origin (#98) Adrian Hope-Bailie
• Re: [w3c/webpayments-payment-apps-api] Multiple payment apps per origin (#98) Adrian Hope-Bailie
• Re: [w3c/webpayments-payment-apps-api] Replace setManifest()/getManifest() with set()/get()/keys()/has()/delete() (#95) Marcos Cáceres
• Re: [w3c/webpayments-payment-apps-api] Multiple payment apps per origin (#98) Marcos Cáceres
• Re: [w3c/webpayments-payment-apps-api] Replace setManifest()/getManifest() with set()/get()/keys()/has()/delete() (#95) Marcos Cáceres
• Re: [w3c/webpayments-payment-apps-api] Replace setManifest()/getManifest() with set()/get()/keys()/has()/delete() (#95) Marcos Cáceres
• Re: [w3c/webpayments-payment-apps-api] Replace setManifest()/getManifest() with set()/get()/keys()/has()/delete() (#95) adamroach
• Re: [w3c/webpayments-payment-apps-api] Replace setManifest()/getManifest() with set()/get()/keys()/has()/delete() (#95) Marcos Cáceres
• Re: [w3c/webpayments-payment-apps-api] Replace setManifest()/getManifest() with set()/get()/keys()/has()/delete() (#95) Marcos Cáceres
• Re: [w3c/webpayments-payment-apps-api] Multiple payment apps per origin (#98) adamroach
• Re: [w3c/webpayments-payment-apps-api] Replace setManifest()/getManifest() with set()/get()/keys()/has()/delete() (#95) adamroach
• Re: [w3c/webpayments-payment-apps-api] Revisiting payment app filtering (#96) ianbjacobs
• Re: [w3c/webpayments-payment-apps-api] Use PaymentRequest and PaymentResponse (#99) Marcos Cáceres
• Re: [w3c/webpayments-payment-apps-api] Use PaymentRequest and PaymentResponse (#99) Marcos Cáceres
• Re: [w3c/webpayments-payment-apps-api] Revisiting payment app filtering (#96) Marcos Cáceres
• Re: [w3c/webpayments-payment-apps-api] Revisiting payment app filtering (#96) Marcos Cáceres
• Re: [w3c/webpayments-payment-apps-api] Replace setManifest()/getManifest() with set()/get()/keys()/has()/delete() (#95) Marcos Cáceres
• Re: [w3c/webpayments-payment-apps-api] Revisiting payment app filtering (#96) Jake Archibald
• Re: [w3c/webpayments-payment-apps-api] Multiple payment apps per origin (#98) Marcos Cáceres
• Re: [w3c/webpayments-payment-apps-api] Replace setManifest()/getManifest() with set()/get()/keys()/has()/delete() (#95) Marcos Cáceres
• Re: [w3c/webpayments-payment-apps-api] Revisiting payment app filtering (#96) adamroach

Tuesday, 24 January 2017

• Re: [w3c/webpayments-payment-apps-api] Multiple payment apps per origin (#98) adamroach
• Re: [w3c/webpayments-payment-apps-api] Revisiting payment app filtering (#96) Adrian Hope-Bailie
• Re: [w3c/webpayments-payment-apps-api] Replace setManifest()/getManifest() with set()/get()/keys()/has()/delete() (#95) Adrian Hope-Bailie
• Re: [w3c/webpayments-payment-apps-api] Multiple payment apps per origin (#98) Adrian Hope-Bailie
• Re: [w3c/webpayments-payment-apps-api] Revisiting payment app filtering (#96) ianbjacobs
• Re: [w3c/webpayments-payment-apps-api] Revisiting payment app filtering (#96) Adrian Hope-Bailie
• Re: [w3c/webpayments-payment-apps-api] Use PaymentRequest and PaymentResponse (#99) Adrian Hope-Bailie
• Re: [w3c/browser-payment-api] `PaymentInstrument.complete(result)` wording (#402) Zach Koch
• Re: [w3c/webpayments-payment-apps-api] Replace setManifest()/getManifest() with set()/get()/keys()/has()/delete() (#95) Mathieu Perreault
• Re: [w3c/webpayments-payment-apps-api] Replace setManifest()/getManifest() with set()/get()/keys()/has()/delete() (#95) adamroach
• Re: [w3c/webpayments-payment-apps-api] Add sentence on display of payment app origin (#100) ianbjacobs
• [w3c/webpayments-payment-apps-api] Add sentence on display of payment app origin (#100) ianbjacobs
• Re: [w3c/webpayments-payment-apps-api] Multiple payment apps per origin (#98) adamroach
• Re: [w3c/webpayments-payment-apps-api] Different approaches to opening windows (#97) adamroach
• Re: [w3c/webpayments-payment-apps-api] Need to specify behavior for Clients.openWindow (#73) ianbjacobs
• Re: [w3c/webpayments-payment-apps-api] Different approaches to opening windows (#97) Dave Longley
• Re: [w3c/webpayments-payment-apps-api] Multiple payment apps per origin (#98) ianbjacobs
• Re: [w3c/webpayments-payment-apps-api] Replace setManifest()/getManifest() with set()/get()/keys()/has()/delete() (#95) Marcos Cáceres
• Re: [w3c/webpayments-payment-apps-api] Multiple payment apps per origin (#98) Marcos Cáceres
• Re: [w3c/webpayments-payment-apps-api] Replace setManifest()/getManifest() with set()/get()/keys()/has()/delete() (#95) ianbjacobs
• Re: [w3c/webpayments-payment-apps-api] Replace setManifest()/getManifest() with set()/get()/keys()/has()/delete() (#95) Marcos Cáceres
• Re: [w3c/webpayments-payment-apps-api] Multiple payment apps per origin (#98) ianbjacobs
• Re: [w3c/webpayments-payment-apps-api] Multiple payment apps per origin (#98) Marcos Cáceres
• Re: [w3c/webpayments-payment-apps-api] Revisiting payment app filtering (#96) ianbjacobs
• Re: [w3c/webpayments-payment-apps-api] Revisiting payment app filtering (#96) Jake Archibald
• Re: [w3c/webpayments-payment-apps-api] Revisiting payment app filtering (#96) Marcos Cáceres
• Re: [w3c/webpayments-payment-apps-api] Revisiting payment app filtering (#96) Marcos Cáceres
• Re: [w3c/webpayments-payment-apps-api] Replace setManifest()/getManifest() with set()/get()/keys()/has()/delete() (#95) ianbjacobs
• Re: [w3c/webpayments-payment-apps-api] Payment app identifier to manifest filename mapping (#48) ianbjacobs
• Re: [w3c/webpayments-payment-apps-api] Replace setManifest()/getManifest() with set()/get()/keys()/has()/delete() (#95) Marcos Cáceres
• Re: [w3c/webpayments-payment-apps-api] Replace setManifest()/getManifest() with set()/get()/keys()/has()/delete() (#95) Marcos Cáceres
• Re: [w3c/webpayments-payment-apps-api] Payment app identifier to manifest filename mapping (#48) Jake Archibald
• Re: [w3c/webpayments-payment-apps-api] Payment app identifier to manifest filename mapping (#48) Tommy Thorsen
• Re: [w3c/webpayments-payment-apps-api] Payment app identifier to manifest filename mapping (#48) Jake Archibald
• Re: [w3c/webpayments-payment-apps-api] Multiple payment apps per origin (#98) Jake Archibald
• Re: [w3c/webpayments-payment-apps-api] Different approaches to opening windows (#97) Jake Archibald
• Re: [w3c/webpayments-payment-apps-api] Revisiting payment app filtering (#96) Tommy Thorsen
• Re: [w3c/webpayments-payment-apps-api] Replace setManifest()/getManifest() with set()/get()/keys()/has()/delete() (#95) Jake Archibald
• Re: [w3c/webpayments-payment-apps-api] Different approaches to opening windows (#97) Marcos Cáceres
• Re: [w3c/webpayments-payment-apps-api] Different approaches to opening windows (#97) Marcos Cáceres
• Re: [w3c/webpayments-payment-apps-api] Multiple payment apps per origin (#98) Marcos Cáceres
• Re: [w3c/webpayments-payment-apps-api] Multiple payment apps per origin (#98) Marcos Cáceres
• Re: [w3c/webpayments-payment-apps-api] Multiple payment apps per origin (#98) Marcos Cáceres
• Re: [w3c/webpayments-payment-apps-api] Replace setManifest()/getManifest() with set()/get()/keys()/has()/delete() (#95) Marcos Cáceres
• Re: [w3c/webpayments-payment-apps-api] Multiple payment apps per origin (#98) Tommy Thorsen
• Re: [w3c/webpayments-payment-apps-api] Replace setManifest()/getManifest() with set()/get()/keys()/has()/delete() (#95) Tommy Thorsen
• Re: [w3c/webpayments-payment-apps-api] Add explicit permission call to allow payment app to handle payments (#94) Jake Archibald
• Re: [w3c/webpayments-payment-apps-api] Revisiting payment app filtering (#96) Jake Archibald
• Re: [w3c/webpayments-payment-apps-api] Use PaymentRequest and PaymentResponse (#99) Marcos Cáceres
• Re: [w3c/webpayments-payment-apps-api] Use PaymentRequest and PaymentResponse (#99) Zach Koch
• Re: [w3c/webpayments-payment-apps-api] Use PaymentRequest and PaymentResponse (#99) Marcos Cáceres
• Re: [w3c/webpayments-payment-apps-api] Use PaymentRequest and PaymentResponse (#99) Marcos Cáceres
• Re: [w3c/webpayments-payment-apps-api] Use PaymentRequest and PaymentResponse (#99) Zach Koch
• Re: [w3c/webpayments-payment-apps-api] Use PaymentRequest and PaymentResponse (#99) ianbjacobs
• Re: [w3c/webpayments-payment-apps-api] Use PaymentRequest and PaymentResponse (#99) Marcos Cáceres
• Re: [w3c/webpayments-payment-apps-api] Use PaymentRequest and PaymentResponse (#99) ianbjacobs
• [w3c/webpayments-payment-apps-api] Use PaymentRequest and PaymentResponse (#99) Marcos Cáceres

Monday, 23 January 2017

• Re: [w3c/webpayments-payment-apps-api] Different approaches to opening windows (#97) Dave Longley
• Re: [w3c/webpayments-payment-apps-api] Payment app identifier to manifest filename mapping (#48) Dave Longley
• [w3c/webpayments-payment-apps-api] Multiple payment apps per origin (#98) adamroach
• [w3c/webpayments-payment-apps-api] Revisiting payment app filtering (#96) adamroach
• [w3c/webpayments-payment-apps-api] Different approaches to opening windows (#97) adamroach
• [w3c/webpayments-payment-apps-api] Replace setManifest()/getManifest() with set()/get()/keys()/has()/delete() (#95) adamroach
• [w3c/webpayments-payment-apps-api] Add explicit permission call to allow payment app to handle payments (#94) adamroach
• Re: [w3c/webpayments-method-identifiers] How should we address payment method manifest files? (#19) Adrian Hope-Bailie
• Re: [w3c/browser-payment-api] Is 'currencySystem' required? (#408) Jinho Bang
• Re: [w3c/browser-payment-api] Is 'currencySystem' required? (#408) ianbjacobs
• Re: [w3c/browser-payment-api] Is 'currencySystem' required? (#408) Tommy Thorsen
• [w3c/browser-payment-api] Is 'currencySystem' required? (#408) Rouslan Solomakhin
• Re: [w3c/webpayments-payment-apps-api] payment-manifest.json and canHandle function (#83) Conor Hackett
• Re: [w3c/webpayments-payment-apps-api] payment-manifest.json and canHandle function (#83) Conor Hackett
• Re: [w3c/webpayments-method-identifiers] How should we address payment method manifest files? (#19) Rouslan Solomakhin
• Re: [w3c/webpayments-payment-apps-api] Payment app identifier to manifest filename mapping (#48) Jake Archibald
• Re: [w3c/webpayments-payment-apps-api] Payment app identifier to manifest filename mapping (#48) Jake Archibald
• Re: [w3c/browser-payment-api] Move state transitions diagram into a note (#406) Marcos Cáceres
• Re: [w3c/browser-payment-api] Move state transitions diagram into a note (#406) Domenic Denicola
• Re: [w3c/browser-payment-api] Move state transitions diagram into a note (#406) Domenic Denicola
• Re: [w3c/browser-payment-api] State how payment details modifier data is serialized and used (#404) Marcos Cáceres
• Re: [w3c/browser-payment-api] Define [[waitForUpdate]] and make it clear where it lives (#407) Marcos Cáceres
• Re: [w3c/browser-payment-api] waitForUpdate is not defined (#371) Marcos Cáceres
• Re: [w3c/browser-payment-api] Move state transitions diagram into a note (#406) Marcos Cáceres
• Re: [w3c/browser-payment-api] State how payment details modifier data is serialized and used (#404) Marcos Cáceres
• Re: [w3c/browser-payment-api] State how payment details modifier data is serialized and used (#404) Marcos Cáceres
• Re: [w3c/browser-payment-api] Setting internal slots of objects from asynchronous steps is not OK (#339) Marcos Cáceres
• Re: [w3c/browser-payment-api] The shipping address/option changed algorithms should not be synchronously poking internal slots (#351) Marcos Cáceres
• Re: [w3c/browser-payment-api] Is it intended that abort() rejects the acceptPromise and resolves its return value in separate tasks? (#340) Marcos Cáceres
• Re: [w3c/browser-payment-api] Queue tasks to change developer-visible properties (#405) Marcos Cáceres
• Re: [w3c/browser-payment-api] Queue tasks to change developer-visible properties (#405) Marcos Cáceres
• Re: [w3c/webpayments-payment-apps-api] Payment app identifier to manifest filename mapping (#48) adamroach
• Re: [w3c/webpayments-payment-apps-api] Payment app identifier to manifest filename mapping (#48) ianbjacobs
• Re: [w3c/webpayments-payment-apps-api] Payment app identifier to manifest filename mapping (#48) Manu Sporny

Sunday, 22 January 2017

• Re: [w3c/webpayments-payment-apps-api] Payment app identifier to manifest filename mapping (#48) Jake Archibald
• Re: [w3c/webpayments-payment-apps-api] Payment app identifier to manifest filename mapping (#48) Adrian Hope-Bailie
• Re: [w3c/webpayments-payment-apps-api] Payment app identifier to manifest filename mapping (#48) adamroach
• Re: [w3c/webpayments-payment-apps-api] Payment app identifier to manifest filename mapping (#48) Adrian Hope-Bailie
• Re: [w3c/webpayments-payment-apps-api] Payment app identifier to manifest filename mapping (#48) Jake Archibald
• Re: [w3c/webpayments-payment-apps-api] Payment app identifier to manifest filename mapping (#48) Adrian Hope-Bailie
• Re: [w3c/webpayments-method-identifiers] How should we address payment method manifest files? (#19) Adrian Hope-Bailie
• Re: [w3c/webpayments-payment-apps-api] Payment app identifier to manifest filename mapping (#48) Jake Archibald
• Re: [w3c/webpayments-payment-apps-api] Payment app identifier to manifest filename mapping (#48) Jake Archibald
• Re: [w3c/webpayments-payment-apps-api] Payment app identifier to manifest filename mapping (#48) Adrian Hope-Bailie
• Re: [w3c/webpayments-payment-apps-api] Payment app identifier to manifest filename mapping (#48) Adrian Hope-Bailie

Saturday, 21 January 2017

• Re: [w3c/browser-payment-api] Why is the "shippingType" member of PaymentOptions not a PaymentShippingType? (#337) ianbjacobs
• Re: [w3c/browser-payment-api] Define [[waitForUpdate]] and make it clear where it lives (#407) Marcos Cáceres
• Re: [w3c/browser-payment-api] Queue tasks to change developer-visible properties (#405) Marcos Cáceres
• Re: [w3c/browser-payment-api] Queue tasks to change developer-visible properties (#405) Domenic Denicola
• Re: [w3c/browser-payment-api] Queue tasks to change developer-visible properties (#405) Marcos Cáceres
• Re: [w3c/browser-payment-api] Need to define the interaction of payment API with navigation and browsing context destruction (#360) Domenic Denicola

Friday, 20 January 2017

• [w3c/browser-payment-api] Define [[waitForUpdate]] and make it clear where it lives (#407) Domenic Denicola
• Re: [w3c/browser-payment-api] waitForUpdate is not defined (#371) Domenic Denicola
• Re: [w3c/browser-payment-api] Why is the "shippingType" member of PaymentOptions not a PaymentShippingType? (#337) Domenic Denicola
• [w3c/browser-payment-api] Move state transitions diagram into a note (#406) Domenic Denicola
• [w3c/browser-payment-api] Queue tasks to change developer-visible properties (#405) Domenic Denicola
• [w3c/browser-payment-api] State how payment details modifier data is serialized and used (#404) Domenic Denicola
• Re: [w3c/webpayments-payment-apps-api] Payment App Decline (#92) ianbjacobs
• Re: [w3c/webpayments-payment-apps-api] Payment App Decline (#92) Dave Longley
• Re: [w3c/webpayments-payment-apps-api] Payment App Decline (#92) rvm4
• Re: [w3c/browser-payment-api] canMakePayment() might be in the wrong place? (#403) Domenic Denicola
• Re: [w3c/webpayments-payment-apps-api] * updates around payment app registration, more clarity wrt user cons… (#93) ianbjacobs
• [w3c/webpayments-payment-apps-api] * updates around payment app registration, more clarity wrt user cons… (#93) ianbjacobs
• Re: [w3c/webpayments-payment-apps-api] Payment App Decline (#92) ianbjacobs
• Re: [w3c/browser-payment-api] canMakePayment() might be in the wrong place? (#403) Marcos Cáceres
• Re: [w3c/browser-payment-api] canMakePayment() might be in the wrong place? (#403) Marcos Cáceres
• Re: [w3c/webpayments-payment-apps-api] Payment app identifier to manifest filename mapping (#48) Jake Archibald
• Re: [w3c/webpayments-payment-apps-api] Payment App Decline (#92) Rouslan Solomakhin
• Re: [w3c/browser-payment-api] canMakePayment() might be in the wrong place? (#403) Rouslan Solomakhin
• Re: [w3c/webpayments-payment-apps-api] Payment app identifier to manifest filename mapping (#48) Rouslan Solomakhin
• Re: [w3c/webpayments-method-identifiers] How should we address payment method manifest files? (#19) Rouslan Solomakhin
• Re: [w3c/webpayments-payment-apps-api] Payment app identifier to manifest filename mapping (#48) Adrian Hope-Bailie
• Re: [w3c/webpayments-payment-apps-api] Payment app identifier to manifest filename mapping (#48) Adrian Hope-Bailie
• Re: [w3c/browser-payment-api] canHandlePayment() might be in the wrong place? (#403) Marcos Cáceres
• [w3c/browser-payment-api] canHandlePayment() might be in the wrong place? (#403) Marcos Cáceres
• Re: [w3c/webpayments-methods-card] Fix typo stating BasicCardRequest as BasicCardResponse (#24) ianbjacobs
• Re: [w3c/webpayments-methods-card] Fix typo stating BasicCardRequest as BasicCardResponse (#24) Marcos Cáceres
• Re: [w3c/webpayments-methods-card] Fix typo stating BasicCardRequest as BasicCardResponse (#24) Marcos Cáceres
• Re: [w3c/webpayments-methods-card] Fix typo stating BasicCardRequest as BasicCardResponse (#24) Marcos Cáceres
• Re: [w3c/webpayments-payment-apps-api] Payment App Decline (#92) Dave Longley

Thursday, 19 January 2017

• Re: [w3c/webpayments-payment-apps-api] Payment App Decline (#92) rvm4
• Re: [w3c/webpayments-payment-apps-api] Payment App Decline (#92) rvm4
• Re: [w3c/webpayments-payment-apps-api] Payment App Decline (#92) Dave Longley
• Re: [w3c/webpayments-payment-apps-api] Payment App Decline (#92) Dave Longley
• [w3c/webpayments-methods-card] Fix typo stating BasicCardRequest as BasicCardResponse (#24) Tri Nguyen
• Re: [w3c/webpayments-payment-apps-api] Payment App Decline (#92) rvm4
• Re: [w3c/webpayments-payment-apps-api] Payment App Decline (#92) ianbjacobs
• Re: [w3c/webpayments-payment-apps-api] Payment App Decline (#92) rvm4
• Re: [w3c/webpayments-payment-apps-api] Payment app identifier to manifest filename mapping (#48) ianbjacobs
• [w3c/browser-payment-api] `PaymentInstrument.complete(result)` wording (#402) Rouslan Solomakhin
• Re: [w3c/webpayments-payment-apps-api] Payment app identifier to manifest filename mapping (#48) Jake Archibald
• Re: [w3c/webpayments-payment-apps-api] Payment app identifier to manifest filename mapping (#48) ianbjacobs
• Re: [w3c/webpayments-payment-apps-api] Payment app identifier to manifest filename mapping (#48) Jake Archibald
• Re: [w3c/webpayments-payment-apps-api] Payment app identifier to manifest filename mapping (#48) ianbjacobs
• Re: [w3c/webpayments-payment-apps-api] Payment App Decline (#92) Tommy Thorsen
• Re: [w3c/webpayments-payment-apps-api] Payment app identifier to manifest filename mapping (#48) Jake Archibald
• Re: [w3c/webpayments-payment-apps-api] Payment app identifier to manifest filename mapping (#48) ianbjacobs
• Re: [w3c/webpayments-payment-apps-api] Payment App Decline (#92) ianbjacobs
• Re: [w3c/browser-payment-api] Editorial: don't capitalize RFC 2119 terms (#377) Marcos Cáceres
• Re: [w3c/browser-payment-api] waitForUpdate is not defined (#371) Dave Longley
• Re: [w3c/browser-payment-api] Phone number format (#390) Marcos Cáceres
• Re: [w3c/browser-payment-api] feat(payment resp algo): phone# SHOULD be E.164 (closes #390) (#396) Marcos Cáceres
• Re: [w3c/browser-payment-api] Editorial: refer to methods with parentheses (closes #378) (#398) Marcos Cáceres
• Re: [w3c/browser-payment-api] Editorial: refer to methods with parentheses (closes #378) (#398) Marcos Cáceres
• Re: [w3c/browser-payment-api] Editorial: refer to methods with parentheses for clarity, and spell out their params in their definition (#378) Marcos Cáceres
• Re: [w3c/browser-payment-api] waitForUpdate is not defined (#371) Domenic Denicola
• Re: [w3c/browser-payment-api] Editorial: don't capitalize RFC 2119 terms (#377) Domenic Denicola
• Re: [w3c/browser-payment-api] Editorial: refer to methods with parentheses (closes #378) (#398) Domenic Denicola
• Re: [w3c/browser-payment-api] Editorial: refer to methods with parentheses (closes #378) (#398) Domenic Denicola
• Re: [w3c/browser-payment-api] Editorial: refer to methods with parentheses (closes #378) (#398) Marcos Cáceres
• Re: [w3c/browser-payment-api] Editorial: refer to methods with parentheses (closes #378) (#398) Marcos Cáceres
• Re: [w3c/browser-payment-api] Editorial: refer to methods with parentheses (closes #378) (#398) Domenic Denicola
• Re: [w3c/browser-payment-api] Editorial: refer to methods with parentheses (closes #378) (#398) Marcos Cáceres
• Re: [w3c/browser-payment-api] Editorial: refer to methods with parentheses (closes #378) (#398) Marcos Cáceres
• Re: [w3c/browser-payment-api] Editorial: refer to methods with parentheses (closes #378) (#398) Marcos Cáceres
• Re: [w3c/browser-payment-api] Editorial: refer to methods with parentheses (closes #378) (#398) Marcos Cáceres
• Re: [w3c/browser-payment-api] Editorial: refer to methods with parentheses (closes #378) (#398) Marcos Cáceres
• Re: [w3c/browser-payment-api] Editorial: refer to methods with parentheses (closes #378) (#398) Marcos Cáceres
• Re: [w3c/browser-payment-api] Editorial: refer to methods with parentheses (closes #378) (#398) Marcos Cáceres
• Re: [w3c/browser-payment-api] Editorial: refer to methods with parentheses (closes #378) (#398) Domenic Denicola
• Re: [w3c/browser-payment-api] Editorial: refer to methods with parentheses (closes #378) (#398) Marcos Cáceres
• Re: [w3c/browser-payment-api] Editorial: refer to methods with parentheses (closes #378) (#398) Marcos Cáceres
• Re: [w3c/browser-payment-api] Editorial: refer to methods with parentheses (closes #378) (#398) Marcos Cáceres
• Re: [w3c/browser-payment-api] Editorial: refer to methods with parentheses (closes #378) (#398) Marcos Cáceres
• Re: [w3c/browser-payment-api] Editorial: refer to methods with parentheses (closes #378) (#398) Marcos Cáceres
• Re: [w3c/browser-payment-api] Editorial: refer to methods with parentheses (closes #378) (#398) Marcos Cáceres
• Re: [w3c/webpayments-payment-apps-api] Payment App Decline (#92) rvm4
• Re: [w3c/webpayments-payment-apps-api] Payment App Decline (#92) Marcos Cáceres
• Re: [w3c/webpayments-payment-apps-api] Payment App Decline (#92) ianbjacobs
• Re: [w3c/browser-payment-api] Editorial: refer to methods with parentheses (closes #378) (#398) Domenic Denicola
• Re: [w3c/webpayments-payment-apps-api] Payment App Decline (#92) rvm4
• Re: [w3c/webpayments-payment-apps-api] Payment App Decline (#92) ianbjacobs
• Re: [w3c/webpayments-payment-apps-api] Payment App Decline (#92) rvm4
• Re: [w3c/browser-payment-api] Editorial: refer to methods with parentheses (closes #378) (#398) Marcos Cáceres
• Re: [w3c/browser-payment-api] Editorial: refer to methods with parentheses (closes #378) (#398) Marcos Cáceres

Wednesday, 18 January 2017

• [w3c/webpayments-payment-apps-api] Payment App Decline (#92) rvm4
• Re: [w3c/browser-payment-api] Editorial: refer to methods with parentheses (closes #378) (#398) Marcos Cáceres
• Re: [w3c/browser-payment-api] Editorial: refer to methods with parentheses (closes #378) (#398) Domenic Denicola
• Re: [w3c/browser-payment-api] Editorial: refer to methods with parentheses (closes #378) (#398) Marcos Cáceres
• [w3c/browser-payment-api] Editorial: firing an event is not done correctly (#401) Domenic Denicola
• Re: [w3c/browser-payment-api] Remove confusing IDL comments (#395) Marcos Cáceres
• [w3c/browser-payment-api] Editorial: Add missing xrefs to various specs (#400) Marcos Cáceres
• Re: [w3c/browser-payment-api] Editorial: use new language for DOMExceptions (close #375) (#397) Marcos Cáceres
• Re: [w3c/browser-payment-api] Editorial: use new language for DOMExceptions (#375) Marcos Cáceres
• Re: [w3c/browser-payment-api] Drop redundant reference to secure context + other redefinitions (#399) Domenic Denicola
• [w3c/browser-payment-api] Drop redundant reference to secure context + other redefinitions (#399) Marcos Cáceres
• Re: [w3c/browser-payment-api] Editorial: use new language for DOMExceptions (close #375) (#397) Domenic Denicola
• Re: [w3c/browser-payment-api] Editorial: use new language for DOMExceptions (close #375) (#397) Marcos Cáceres
• Re: [w3c/browser-payment-api] Editorial: use new language for DOMExceptions (close #375) (#397) Marcos Cáceres
• Re: [w3c/browser-payment-api] Editorial: use new language for DOMExceptions (close #375) (#397) Marcos Cáceres
• Re: [w3c/browser-payment-api] Editorial: refer to methods with parentheses (closes #378) (#398) Domenic Denicola
• Re: [w3c/browser-payment-api] Editorial: use new language for DOMExceptions (close #375) (#397) Marcos Cáceres
• Re: [w3c/browser-payment-api] Editorial: use new language for DOMExceptions (close #375) (#397) Domenic Denicola
• Re: [w3c/browser-payment-api] feat(payment resp algo): phone# SHOULD be E.164 (closes #390) (#396) Rouslan Solomakhin
• Re: [w3c/browser-payment-api] DOMExceptions are now in WebIDL (#314) Marcos Cáceres
• Re: [w3c/browser-payment-api] DOMExceptions are now in WebIDL (#314) Marcos Cáceres
• Re: [w3c/browser-payment-api] Editorial: refer to methods with parentheses (closes #378) (#398) Marcos Cáceres
• [w3c/browser-payment-api] Editorial: refer to methods with parentheses (closes #378) (#398) Marcos Cáceres
• Re: [w3c/browser-payment-api] Editorial: don't capitalize RFC 2119 terms (#377) Marcos Cáceres
• Re: [w3c/browser-payment-api] Editorial: refer to methods with parentheses for clarity, and spell out their params in their definition (#378) Marcos Cáceres
• Re: [w3c/browser-payment-api] feat(payment resp algo): phone# SHOULD be E.164 (closes #390) (#396) Marcos Cáceres
• Re: [w3c/browser-payment-api] Editorial: use new language for DOMExceptions (close #375) (#397) Marcos Cáceres
• [w3c/browser-payment-api] Editorial: use new language for DOMExceptions (close #375) (#397) Marcos Cáceres
• Re: [w3c/webpayments-payment-apps-api] Need to specify behavior for Clients.openWindow (#73) ianbjacobs
• Re: [w3c/webpayments-payment-apps-api] Why does a Payment App need to see the line items? (#91) ianbjacobs
• [w3c/webpayments-payment-apps-api] Why does a Payment App need to see the line items? (#91) Zach Koch
• Re: [w3c/webpayments-payment-apps-api] Clarification on Payment App "Options" (#90) ianbjacobs
• Re: [w3c/webpayments-payment-apps-api] Clarification on Payment App "Options" (#90) Zach Koch
• [w3c/webpayments-payment-apps-api] Clarification on Payment App "Options" (#90) Zach Koch
• Re: [w3c/webpayments-payment-apps-api] Need to specify behavior for Clients.openWindow (#73) Jenan Wise

Tuesday, 17 January 2017

• Re: [w3c/webpayments-payment-apps-api] Updates around display of windows (#89) ianbjacobs
• Re: [w3c/webpayments-payment-apps-api] Small fixes + displayItems (#88) ianbjacobs
• Re: [w3c/webpayments-payment-apps-api] Small fixes + displayItems (#88) ianbjacobs
• Re: [w3c/webpayments-payment-apps-api] Small fixes + displayItems (#88) Adrian Hope-Bailie
• Re: [w3c/webpayments-payment-apps-api] Updates around display of windows (#89) Adrian Hope-Bailie
• [w3c/webpayments-payment-apps-api] Updates around display of windows (#89) ianbjacobs
• [w3c/webpayments-payment-apps-api] Small fixes + displayItems (#88) ianbjacobs
• Re: [w3c/webpayments-payment-apps-api] We need a PaymentAppResponseData dictionary (#81) ianbjacobs
• Re: [w3c/webpayments-payment-apps-api] We need a PaymentAppResponseData dictionary (#81) ianbjacobs
• Re: [w3c/webpayments-payment-apps-api] payment-manifest.json and canHandle function (#83) ianbjacobs
• Re: [w3c/webpayments-payment-apps-api] payment-manifest.json and canHandle function (#83) adamroach
• Re: [w3c/webpayments-payment-apps-api] Payment app identifier to manifest filename mapping (#48) Dave Longley
• Re: [w3c/webpayments-payment-apps-api] Payment app identifier to manifest filename mapping (#48) Jake Archibald
• Re: [w3c/webpayments-payment-apps-api] Introduce the PaymentAppResponseData dictionary (#84) ianbjacobs
• Re: [w3c/webpayments-payment-apps-api] Payment app identifier to manifest filename mapping (#48) Dave Longley
• Re: [w3c/webpayments-payment-apps-api] Payment app identifier to manifest filename mapping (#48) ianbjacobs
• Re: [w3c/webpayments-payment-apps-api] Payment app identifier to manifest filename mapping (#48) Jake Archibald
• Re: [w3c/webpayments-payment-apps-api] Need to specify behavior for Clients.openWindow (#73) Tommy Thorsen
• [w3c/browser-payment-api] feat(payment resp algo): phone# SHOULD be E.164 (closes #390) (#396) Marcos Cáceres
• [w3c/browser-payment-api] Remove confusing IDL comments (#395) Marcos Cáceres
• Re: [w3c/browser-payment-api] Internal slots vs. attributes (#393) Marcos Cáceres
• Re: [w3c/browser-payment-api] Internal slots vs. attributes (#393) Marcos Cáceres
• Re: [w3c/webpayments-method-identifiers] SRI on manifest (#18) Marcos Cáceres
• Re: [w3c/webpayments-method-identifiers] How should we address payment method manifest files? (#19) Mark Nottingham

Monday, 16 January 2017

• Re: [w3c/browser-payment-api] The "data" member of PaymentDetailsModifier doesn't seem to be used for anything (#346) Rouslan Solomakhin
• Re: [w3c/browser-payment-api] [WebIDL] reference is wrong (#394) Marcos Cáceres
• Re: [w3c/browser-payment-api] [WebIDL] reference is wrong (#394) Marcos Cáceres
• Re: [w3c/browser-payment-api] [WebIDL] reference is wrong (#394) Marcos Cáceres
• Re: [w3c/browser-payment-api] [WebIDL] reference is wrong (#394) Marcos Cáceres
• Re: [w3c/browser-payment-api] [WebIDL] reference is wrong (#394) Domenic Denicola
• Re: [w3c/browser-payment-api] [WebIDL] reference is wrong (#394) Tobie Langel
• Re: [w3c/browser-payment-api] [WebIDL] reference is wrong (#394) Marcos Cáceres
• Re: [w3c/browser-payment-api] [WebIDL] reference is wrong (#394) Domenic Denicola
• Re: [w3c/browser-payment-api] [WebIDL] reference is wrong (#394) Tobie Langel
• Re: [w3c/browser-payment-api] [WebIDL] reference is wrong (#394) Tobie Langel
• Re: [w3c/browser-payment-api] [WebIDL] reference is wrong (#394) Marcos Cáceres
• Re: [w3c/browser-payment-api] Internal slots vs. attributes (#393) Marcos Cáceres

Sunday, 15 January 2017

• Re: [w3c/browser-payment-api] [WebIDL] reference is wrong (#394) Marcos Cáceres
• Re: [w3c/browser-payment-api] fix(payment request algo): set attributes to null if not given (closes #385) (#391) Marcos Cáceres

Saturday, 14 January 2017

• Re: [w3c/browser-payment-api] The "data" member of PaymentDetailsModifier doesn't seem to be used for anything (#346) Domenic Denicola
• Re: [w3c/browser-payment-api] fix(payment request algo): set attributes to null if not given (closes #385) (#391) Domenic Denicola
• [w3c/browser-payment-api] [WebIDL] reference is wrong (#394) Domenic Denicola
• Re: [w3c/browser-payment-api] fix(payment request algo): set attributes to null if not given (closes #385) (#391) Marcos Cáceres
• Re: [w3c/browser-payment-api] style(index.html): cleanup markup (#392) Marcos Cáceres
• Re: [w3c/browser-payment-api] style(index.html): cleanup markup (#392) Marcos Cáceres
• Re: [w3c/browser-payment-api] style(index.html): cleanup markup (#392) Domenic Denicola

Friday, 13 January 2017

• Re: [w3c/webpayments-payment-apps-api] Security note adjustment (#87) ianbjacobs
• [w3c/webpayments-payment-apps-api] Security note adjustment (#87) ianbjacobs
• Re: [w3c/webpayments-payment-apps-api] Move secure context note from intro to where the requirement is listed. (#85) ianbjacobs
• Re: [w3c/webpayments-payment-apps-api] Move secure context note from intro to where the requirement is listed. (#85) ianbjacobs
• Re: [w3c/webpayments-payment-apps-api] security note moved (#86) ianbjacobs
• Re: [w3c/webpayments-payment-apps-api] Move secure context note from intro to where the requirement is listed. (#85) ianbjacobs
• Re: [w3c/webpayments-payment-apps-api] Move secure context note from intro to where the requirement is listed. (#85) ianbjacobs
• [w3c/webpayments-payment-apps-api] security note moved (#86) ianbjacobs
• Re: [w3c/webpayments-payment-apps-api] Edits based on recent discussions and decisions (#80) ianbjacobs
• Re: [w3c/webpayments-payment-apps-api] Edits based on recent discussions and decisions (#80) ianbjacobs
• Re: [w3c/webpayments-payment-apps-api] Edits based on recent discussions and decisions (#80) ianbjacobs
• Re: [w3c/webpayments-payment-apps-api] We need a PaymentAppResponseData dictionary (#81) ianbjacobs

Thursday, 12 January 2017

• [w3c/webpayments-payment-apps-api] Move secure context note from intro to where the requirement is listed. (#85) ianbjacobs
• Re: [w3c/webpayments-payment-apps-api] Edits based on recent discussions and decisions (#80) ianbjacobs
• Re: [w3c/webpayments-payment-apps-api] How does the payee provide information about recommended payment apps? (#79) ianbjacobs
• Re: [w3c/webpayments-payment-apps-api] Introduce the PaymentAppResponseData dictionary (#84) ianbjacobs
• Re: [w3c/webpayments-payment-apps-api] Introduce the PaymentAppResponseData dictionary (#84) Tommy Thorsen
• Re: [w3c/webpayments-payment-apps-api] Introduce the PaymentAppResponseData dictionary (#84) Dave Longley
• Re: [w3c/webpayments-payment-apps-api] We need a PaymentAppResponseData dictionary (#81) Tommy Thorsen
• [w3c/webpayments-payment-apps-api] Introduce the PaymentAppResponseData dictionary (#84) Tommy Thorsen
• Re: [w3c/browser-payment-api] Internal slots vs. attributes (#393) Tommy Thorsen

Wednesday, 11 January 2017

• Re: [w3c/browser-payment-api] The myth of JSON-serializable object (#307) Zach Koch
• Re: [w3c/browser-payment-api] The myth of JSON-serializable object (#307) Zach Koch
• Re: [w3c/browser-payment-api] Internal slots vs. attributes (#393) Domenic Denicola
• Re: [w3c/browser-payment-api] Invoke "allowed to use" always (#383) Zach Koch
• Re: [w3c/browser-payment-api] Security hole in payment API when a constructor from a no longer active document is invoked (#361) Zach Koch
• Re: [w3c/browser-payment-api] fix(payment request algo): set attributes to null if not given (closes #385) (#391) Zach Koch
• Re: [w3c/browser-payment-api] The myth of JSON-serializable object (#307) Domenic Denicola
• Re: [w3c/browser-payment-api] The myth of JSON-serializable object (#307) Zach Koch
• Re: [w3c/browser-payment-api] Ambiguous conformance requirement in constructor (#354) Zach Koch
• Re: [w3c/browser-payment-api] The "data" member of PaymentMethodData doesn't seem to actually be used for anything (#338) Zach Koch
• Re: [w3c/browser-payment-api] Straighten out the payment method data flow (#382) Zach Koch
• Re: [w3c/browser-payment-api] Invoke "allowed to use" always (#383) Ade Bateman
• Re: [w3c/browser-payment-api] style(index.html): cleanup markup (#392) Ade Bateman
• Re: [w3c/browser-payment-api] fix(payment request algo): set attributes to null if not given (closes #385) (#391) Ade Bateman
• Re: [w3c/browser-payment-api] Straighten out the payment method data flow (#382) Ade Bateman
• Re: [w3c/webpayments-payment-apps-api] payment-manifest.json and canHandle function (#83) Rouslan Solomakhin

Tuesday, 10 January 2017

• [w3c/webpayments-payment-apps-api] payment-manifest.json and canHandle function (#83) Conor Hackett
• [w3c/webpayments-methods-card] Say how we integrate with PaymentRequest (#23) Domenic Denicola
• Re: [w3c/webpayments-payment-apps-api] Example 3 does not work (#82) Tommy Thorsen
• Re: [w3c/browser-payment-api] Straighten out the payment method data flow (#382) Domenic Denicola
• Re: [w3c/webpayments-payment-apps-api] How does the payee provide information about recommended payment apps? (#79) ianbjacobs
• Re: [w3c/webpayments-payment-apps-api] Example 3 does not work (#82) Dave Longley
• Re: [w3c/browser-payment-api] Providing/Generating paymentRequestID during construction (#388) Rouslan Solomakhin
• Re: [w3c/browser-payment-api] Phone number format (#390) Rouslan Solomakhin
• Re: [w3c/webpayments-payment-apps-api] Example 3 does not work (#82) adamroach
• Re: [w3c/webpayments-payment-apps-api] Example 3 does not work (#82) Rouslan Solomakhin
• Re: [w3c/browser-payment-api] Phone number format (#390) Nick Shearer
• Re: [w3c/browser-payment-api] Serializer behavior (#385) Rouslan Solomakhin
• Re: [w3c/browser-payment-api] fix(payment request algo): set attributes to null if not given (closes #385) (#391) Domenic Denicola
• Re: [w3c/browser-payment-api] Straighten out the payment method data flow (#382) Domenic Denicola
• Re: [w3c/browser-payment-api] Providing/Generating paymentRequestID during construction (#388) ianbjacobs
• [w3c/browser-payment-api] Internal slots vs. attributes (#393) Tommy Thorsen
• Re: [w3c/webpayments-payment-apps-api] We need a PaymentAppResponseData dictionary (#81) Tommy Thorsen
• [w3c/webpayments-payment-apps-api] Example 3 does not work (#82) Tommy Thorsen
• [w3c/webpayments-payment-apps-api] We need a PaymentAppResponseData dictionary (#81) Tommy Thorsen
• [w3c/browser-payment-api] style(index.html): cleanup markup (#392) Marcos Cáceres
• [w3c/browser-payment-api] fix(payment request algo): set attributes to null if not given (closes #385) (#391) Marcos Cáceres
• Re: [w3c/browser-payment-api] Serializer behavior (#385) Marcos Cáceres
• Re: [w3c/browser-payment-api] Providing/Generating paymentRequestID during construction (#388) Marcos Cáceres
• Re: [w3c/browser-payment-api] Providing/Generating paymentRequestID during construction (#388) Marcos Cáceres
• Re: [w3c/browser-payment-api] Examples in the spec (#274) Marcos Cáceres
• Re: [w3c/browser-payment-api] Examples in the spec (#274) Marcos Cáceres
• Re: [w3c/browser-payment-api] Phone number format (#390) Marcos Cáceres
• Re: [w3c/browser-payment-api] Straighten out the payment method data flow (#382) Marcos Cáceres
• Re: [w3c/browser-payment-api] Invoke "allowed to use" always (#383) Marcos Cáceres
• Re: [w3c/browser-payment-api] Invoke "allowed to use" always (#383) Marcos Cáceres
• Re: [w3c/browser-payment-api] Straighten out the payment method data flow (#382) Marcos Cáceres

Monday, 9 January 2017

• Re: [w3c/browser-payment-api] Providing/Generating paymentRequestID during construction (#388) ianbjacobs
• Re: [w3c/browser-payment-api] Providing/Generating paymentRequestID during construction (#388) Marcos Cáceres

Friday, 6 January 2017

• Re: [w3c/browser-payment-api] Phone number format (#390) Nick Shearer
• Re: [w3c/browser-payment-api] Phone number format (#390) ianbjacobs
• [w3c/browser-payment-api] Phone number format (#390) Rouslan Solomakhin
• Re: [w3c/webpayments-payment-apps-api] What is matching and display behavior for various scenarios of recommended apps, enabled apps, non-enabled apps, etc.? (#38) ianbjacobs
• Re: [w3c/webpayments-payment-apps-api] What is matching and display behavior for various scenarios of recommended apps, enabled apps, non-enabled apps, etc.? (#38) ianbjacobs
• Re: [w3c/webpayments-payment-apps-api] Should we allow payment providers to issue queries about their installed payment apps (match on origin) (#6) ianbjacobs
• Re: [w3c/webpayments-payment-apps-api] Should we allow payment providers to issue queries about their installed payment apps (match on origin) (#6) ianbjacobs
• Re: [w3c/webpayments-payment-apps-api] Versioning (#45) ianbjacobs
• Re: [w3c/webpayments-payment-apps-api] Versioning (#45) ianbjacobs
• Re: [w3c/webpayments-payment-apps-api] Section 6 steps 1-5 seem to avoid selecting a payment option / payment method (#56) ianbjacobs
• Re: [w3c/webpayments-payment-apps-api] Section 6 steps 1-5 seem to avoid selecting a payment option / payment method (#56) ianbjacobs
• Re: [w3c/browser-payment-api] Invoke "allowed to use" always (#383) ockxdd

Thursday, 5 January 2017

• [w3c/webpayments-payment-apps-api] Edits based on recent discussions and decisions (#80) ianbjacobs
• [w3c/webpayments-payment-apps-api] How does the payee provide information about recommended payment apps? (#79) ianbjacobs
• Re: [w3c/webpayments-payment-apps-api] Split out enabled and supported methods (#7) ianbjacobs
• Re: [w3c/webpayments-payment-apps-api] Split out enabled and supported methods (#7) ianbjacobs
• Re: [w3c/webpayments-payment-apps-api] Should payment apps implement payment method-specific filters? (#63) ianbjacobs
• Re: [w3c/webpayments-payment-apps-api] Should payment apps implement payment method-specific filters? (#63) ianbjacobs
• Re: [w3c/webpayments-method-identifiers] Why are payment ids restricted to [a-z0-9]? (#20) ianbjacobs
• Re: [w3c/webpayments-method-identifiers] How should we address payment method manifest files? (#19) ianbjacobs
• [w3c/webpayments-method-identifiers] Why are payment ids restricted to [a-z0-9]? (#20) stevenatkin
• Re: [w3c/browser-payment-api] Add canMakePayment() method (#380) Jeff Burdges
• Re: [w3c/browser-payment-api] Add canMakePayment() method (#380) Domenic Denicola
• Re: [w3c/browser-payment-api] Invoke "allowed to use" always (#383) ianbjacobs
• Re: [w3c/browser-payment-api] Invoke "allowed to use" always (#383) Simon Pieters
• Re: [w3c/browser-payment-api] Add canMakePayment() method (#380) Jeff Burdges
• Re: [w3c/browser-payment-api] "contains a value for" isn't defined for dictionaries (#321) Michael[tm] Smith
• Re: [w3c/browser-payment-api] "contains a value for" isn't defined for dictionaries (#321) Michael[tm] Smith
• Re: [w3c/browser-payment-api] Straighten out the payment method data flow (#382) Domenic Denicola
• Re: [w3c/browser-payment-api] Straighten out the payment method data flow (#382) Ade Bateman
• Re: [w3c/browser-payment-api] "contains a value for" isn't defined for dictionaries (#321) Domenic Denicola

Wednesday, 4 January 2017

• Re: [w3c/browser-payment-api] an event to providing standards for push payment methods (#223) Marcos Cáceres
• Re: [w3c/browser-payment-api] an event to providing standards for push payment methods (#223) Marcos Cáceres
• Re: [w3c/browser-payment-api] Add `enableLegacyCheckout` option to PaymentOptions. (#365) Marcos Cáceres
• Re: [w3c/browser-payment-api] Add `enableLegacyCheckout` option to PaymentOptions. (#365) Marcos Cáceres
• Re: [w3c/browser-payment-api] A PaymentDetailsModifier may not have an additionalDisplayItems value present (#335) Marcos Cáceres
• Re: [w3c/browser-payment-api] Various fixes to the PaymentRequest constructor (#374) Marcos Cáceres
• Re: [w3c/browser-payment-api] Various fixes to the PaymentRequest constructor (#374) Ade Bateman
• Re: [w3c/browser-payment-api] PaymentRequest constructor validation ordering does not match Blink at all (#373) Marcos Cáceres
• Re: [w3c/browser-payment-api] A `PaymentItem` can't be a "valid decimal monetary value" (#334) Marcos Cáceres
• Re: [w3c/browser-payment-api] PaymentDetails may not have values present for various sequences, but the PaymentRequest constructor assumes that it does (#333) Marcos Cáceres
• Re: [w3c/browser-payment-api] Straighten out the payment method data flow (#382) Domenic Denicola
• Re: [w3c/browser-payment-api] Straighten out the payment method data flow (#382) Ade Bateman
• Re: [w3c/webpayments-payment-apps-api] Suggested apps (#74) ianbjacobs
• Re: [w3c/webpayments-payment-apps-api] Need to specify behavior for Clients.openWindow (#73) ianbjacobs
• Re: [w3c/webpayments-payment-apps-api] (Deleted this edit by mistake before merged) (#78) ianbjacobs
• Re: [w3c/webpayments-payment-apps-api] Lambda functions for app matching (#76) ianbjacobs
• Re: [w3c/webpayments-payment-apps-api] Lambda functions for app matching (#76) adamroach

Tuesday, 3 January 2017

• Re: [w3c/webpayments-payment-apps-api] Need to specify behavior for Clients.openWindow (#73) Jenan Wise
• Re: [w3c/webpayments-payment-apps-api] Need to specify behavior for Clients.openWindow (#73) ianbjacobs
• Re: [w3c/browser-payment-api] PaymentRequest does not handle the case of store pickup (#389) Rouslan Solomakhin
• Re: [w3c/browser-payment-api] PaymentRequest does not handle the case of store pickup (#389) ianbjacobs
• Re: [w3c/browser-payment-api] PaymentRequest does not handle the case of store pickup (#389) Rouslan Solomakhin
• [w3c/browser-payment-api] PaymentRequest does not handle the case of store pickup (#389) sanjoypal
• [w3c/browser-payment-api] Providing paymentRequestID during construction (#388) sanjoypal

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