Re: [w3c/payment-request] Clarify when the user can abort the payment request algorithm (#796)

@aestes wrote: 
> You can get stuck in (1) as well, since it's up to the merchant to resolve the PaymentDetailsUpdate promise. 
> Safari imposes a timeout there too.

Ok, that makes sense. I'll update the spec to:

 1. Allow a timeout. 
 1. Make it clear that the browser may provide a means to abort the payment, even if the pay button and other input fields are disabled. 

> I think users should not be allowed to cancel after they accept the payment. Once a PaymentResponse is returned to the merchant it's probably too late to expect the user abort to be honored in all cases, so users shouldn't be made to think otherwise.

Ok, would it be possible to report back on 2? If both Chrome and Safari allow it, we might need to revise the spec text (or rephrase this as a SHOULD). Firefox currently conforms to the spec. 

-- 
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/796#issuecomment-440140793