W3C home > Mailing lists > Public > public-payments-wg@w3.org > December 2015

Re: [webpayments] Should we expose status change events in the browser API? (#41)

From: Dave Longley <notifications@github.com>
Date: Thu, 17 Dec 2015 08:52:32 -0800
To: w3c/webpayments <webpayments@noreply.github.com>
Message-ID: <w3c/webpayments/issues/41/165507646@github.com>

@zkoch,

I'm sure they are quite busy, but if possible it may be a good idea to request feedback from @domenic and @jakearchibald.

---
Reply to this email directly or view it on GitHub:
https://github.com/w3c/webpayments/issues/41#issuecomment-165507646

Received on Thursday, 17 December 2015 16:53:35 UTC

This message: [ Message body ]
Next message: Web Payments Working Group Issue Tracker: "wpwg-ACTION-10: Integrate standard flow into web payments cg's browser api spec."
Previous message: Dave Longley: "Re: [webpayments] Should a Payment Request API have shipping address APIs? (#39)"
In reply to: Manu Sporny: "[webpayments] Should we expose status change events in the browser API? (#41)"
Next in thread: Adrian Hope-Bailie: "Re: [webpayments] Should we expose status change events in the browser API? (#41)"

Mail actions: [ respond to this message ] [ mail a new topic ]
Contemporary messages sorted: [ by date ] [ by thread ] [ by subject ] [ by author ]
Help: [ How to use the archives ] [ Search in the archives ]

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:43:12 UTC