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:15:31 -0800
To: w3c/webpayments <webpayments@noreply.github.com>
Message-ID: <w3c/webpayments/issues/41/165497775@github.com>
> When it's all said and done, I think we'll limit the amount of time a merchant has to call the update() method after an event is emitted.

I believe this can be solved much more elegantly by making the collection of address information a separate operation. This would also allow the merchant to collect this information at a time that works for them and their flow. As it stands today, if a merchant wants or needs to collect this information at a different time (eg: earlier in the shopping/checkout process), they will not be able to use this API.

> Thanks for other comments as well. Need a bit more time to process and think about them. Will circle back.


Reply to this email directly or view it on GitHub:
Received on Thursday, 17 December 2015 16:16:36 UTC

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