- From: John-David Dalton <notifications@github.com>
- Date: Thu, 07 Dec 2017 17:46:09 -0800
- To: w3c/payment-request <payment-request@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Friday, 8 December 2017 01:46:33 UTC
I noticed the doc note [here](https://www.w3.org/TR/payment-request/#updatewith()-method): > If a developer wants to update the payment request, then they need to call updateWith() and provide a PaymentDetailsUpdate dictionary, or a promise for one, containing changed values that the user agent presents to the user. The bit that's interesting is the a developer may provide a PaymentDetailsUpdate dictionary object *(so not a promise)* but the IDL and the spec steps describe only the `detailsPromise`. Google dev docs show `updateWith` accepting a vanilla object too ([here](https://developers.google.com/web/fundamentals/payments/deep-dive-into-payment-request#defining_the_available_shipping_options) and [here](https://developers.google.com/web/fundamentals/payments/deep-dive-into-payment-request#customizing_the_shipping_options_error)). And Google's implementation appears to accept vanilla objects too. Does the spec text need to be updated or am I missing something? -- 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/payment-request/issues/657
Received on Friday, 8 December 2017 01:46:33 UTC