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

The currently specified behaviour leads to a really bad/confusing experience when comparison shopping so I agree the spec should change. Firefox doesn't plan to require only one active payment request because of the bad UX it would provide so we are wilfully violating the spec currently and because of this I think it should be a CR-exit issue.

> What I think we want is: if required by the Payment Handler, if Site A is showing a payment sheet, and Site B tries to show a payment sheet, then Site A's payment gets aborted.

That is also bad because it causes dataloss for anything the user had typed into the Payment Request dialog that wasn't saved into persistent storage. I think that's better than the current state since basic-card wouldn't have this requirement but I think it wouldn't be a good behaviour for any payment method that could have dataloss if it gets randomly aborted by another tab.

For v.1 it may make sense to just remove the single "payment request is showing" requirement from the spec altogether.

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