- From: Adrian Hope-Bailie <notifications@github.com>
- Date: Fri, 29 Apr 2016 01:39:17 -0700
- To: w3c/browser-payment-api <browser-payment-api@noreply.github.com>
- Cc:
Received on Friday, 29 April 2016 08:39:48 UTC
Somewhat related to some of the discussion in #75 as ShippingAddress is a a good example of response data that could (in future) be provided by the payment app not the user agent. Currently the user agent gathered data hangs directly off the response object (`response.shippingAddress`) and the data from the payment app does too (`response.details`). If the payment app returned the shippingAddress (or some other data that the website had requested) would it sit at `response.shippingAddress` or `response.details.shippingAddress`? --- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3c/browser-payment-api/issues/173
Received on Friday, 29 April 2016 08:39:48 UTC