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

@adamroach this processing is intended to happen before the user agent has passed the payment request to the payment app so payment apps are not involved in this processing at all.

However, I think this is still a valid issue for the editors to address:
> The procedure in section 13.2 does not mention any processing steps in the case the update promise d is rejected.

Also, the case where d is resolved but is not a valid PaymentDetails dictionary


---
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-218706446