- From: Ade Bateman <notifications@github.com>
- Date: Wed, 08 Jun 2016 08:44:52 -0700
- To: w3c/browser-payment-api <browser-payment-api@noreply.github.com>
- Cc:
Received on Wednesday, 8 June 2016 15:45:47 UTC
This is a proposal for how to handle #187. It causes the payment request to be aborted if the promise passed to `updateWith()` is then rejected. If the promise passed to `updateWith()` is rejected then you end up in an inconsistent state. Either the page hasn't correctly processed the change event (which might mean it didn't correctly update the price, for example) or, if you revert the user's change, the user may end up in a state that they didn't expect. Neither option is good. Instead, after discussion with @zkoch, we're proposing that this aborts the payment request. You can view, comment on, or merge this pull request online at: https://github.com/w3c/browser-payment-api/pull/209 -- Commit Summary -- * Proposal to abort if updateWith promise is rejected -- File Changes -- M index.html (190) -- Patch Links -- https://github.com/w3c/browser-payment-api/pull/209.patch https://github.com/w3c/browser-payment-api/pull/209.diff --- 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/209
Received on Wednesday, 8 June 2016 15:45:47 UTC