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

@adrianhopebailie wrote: 
> 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). 

Yes. So a neat thing about the current design is that it handles not showing multiple payments sheets in a single browser window or tab (I know, that would be really silly and no one would do that... but it's a happy coincidence we have that protection in the spec!). 

So, by simply changing "user agent's payment request is showing boolean" to "top-level browsing context's payment request is showing boolean" we get the behavior we want 🏆. Then, we just need to add a note that payment handlers might do different things when handling multiple simultaneous requests for payment. 

I'll draft something up. 

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

Depends... again, see what I wrote about Apple Pay. It's not surprising in that context because of how Apple Pay hooks up to a phone or watch. But I can imagine a situation where a user is verifying a payment manually (without a phone or watch), in which case, it could be theoretically possible to show multiple payment sheets in separate browser windows/tabs.   

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

No. I can't think of any.  

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