Re: [w3c/payment-request] Rethink "payment request is showing" boolean (#809)

Sounds like the consensus is to at least drop the restriction as a CR-Exit requirement, is that correct?

I think we can do that in a way that ensures the complexity of parallel requests is dealt with in PH API spec not PR API. (I.e. the flag is simply per context not global)

@marcoscaceres you said:
> consider, a web page can't arbitrarily cause another sheet to be closed down without the user explicitly clicking on another pay button.

This seems like a very surprising user experience, performing an action on one tab having an impact on another, no?

In any case, I'm not too concerned about Payment Handlers needing to deal with parallel request, I think it will be trivial for them to do this.  I think we can put that aside in deciding what to do with PR API for CR.

Are there any other reasons, besides "user confusion", to limit the browser to only a single global payment sheet?

-- 
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/809#issuecomment-440176201