You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 and here).
And Google's implementation appears to accept vanilla objects too.
Does the spec text need to be updated or am I missing something?
The text was updated successfully, but these errors were encountered:
Just to clarify further on @romandev's comment, WebIDL autowraps parameters of promise-accepting methods: so updateWith(details) and updateWith(Promise.resolve(details)) are, from a developer perspective, equivalent.
I noticed the doc note here (or here):
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 and here).And Google's implementation appears to accept vanilla objects too.
Does the spec text need to be updated or am I missing something?
The text was updated successfully, but these errors were encountered: