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

> For example, when a shipping address changes, what if the merchant website needs to perform an async request to obtain updated pricing information?

This is actually the exact use case we're trying to support. :) 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. Still thinking about that and working out details, though.

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 15:59:31 UTC