Re: [w3c/browser-payment-api] Make updateWith() return a promise signaling any update failures (#418)

By the way, Chrome does not ignore invalid data in `updateWith()`. It validates the provided `PaymentDetails` in the same way as the constructor for `PaymentRequest`. If `PaymentDetails` is invalid, then `updateWith()` throws the same exceptions as the constructor. The only difference is that the constructor prohibits use of `PaymentDetails.error`, which is OK to use in `updateWith()`.

If validation of `PaymentDetails` is the only concern for `updateWith()`, should we stick with exceptions, because that validation can be performed synchronously.

-- 
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/pull/418#issuecomment-281366646

Received on Tuesday, 21 February 2017 14:55:41 UTC