FWIW, ApplePay on Safari also seems to restrict to once per browser instance: it throws if you try to spin up two sessions. It's not clear to me what exception it is throwing tho (in Safari's dev tools, it looks like it's just throwing text :-/... but not sure.). You can test it here: https://stripe.com/docs/apple-pay/web Having the ability to only spin up a single payment request at a time seems sensible though. We should standardize on that (Chrome/Safari) behavior. So `AbortError` would be ok, but maybe `InvalidStateError` would be better - because abort really signals that the user aborted. -- 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/browser-payment-api/issues/462#issuecomment-289634437
Received on Tuesday, 28 March 2017 01:24:13 UTC