Re: [w3c/browser-payment-api] Update promise rejection (#187)

@adrianhopebailie, I believe this is all handled in the algorithm. It makes a rejected promise a no-op. It also extracts appropriate data from PaymentDetails and ignores other details.

As I said in mail, I disagree that _the only sensible thing to do is to revert the change that the user made which triggered the event_.

---
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/187#issuecomment-218742996