Re: [w3c/payment-request] Retrying a payment (#705)

I've been investigating how to do add `.retry()` over the last few days... Because of the way we originally wrote the spec, we never assumed `PaymentRequest` and `PaymentResponse` would take the same code paths (or that the `PaymentResponse` would need a state machine)... thus, the spec is heavily biased towards `PaymentRequest` in all its algorithms, and to change it means a significant rewrite. 

Because of this, I'm going to investigate restarting the `PaymentRequest` state machine. Thus, going to see what happens if `.retry()` puts `PaymentRequest` into the "interactive" state... and then we can figure out where to fire `payerdetailschange`. 

-- 
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/payment-request/issues/705#issuecomment-390596746