- From: Matt Saxon <notifications@github.com>
- Date: Mon, 18 Feb 2019 05:58:05 -0800
- To: w3c/payment-request <payment-request@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Monday, 18 February 2019 13:58:27 UTC
Thanks @marcoscaceres. I agree that the full details of my proposal are beyond the spec, but I think there are a few items in the spec that could do with amending to allow this sort of approach. For example the spec current states; > It is not possible to show multiple PaymentRequests at the same time within one user agent. If a PaymentRequest is already showing, calling show() —from any Web site— will return a promise rejected with an "AbortError" DOMException. With the approach I outline, I don't think the restriction in the specification needs to apply. I think this restriction was inserted on the basis that the interactions after .show() was expected to be modal. Furthermore I think some of other wording implies a modal approach, for example > ....when the user accepts the payment request. I would suggest this could read 'if the user were to authorize a payment request" If we can remove the expectations around modality from the spec, then I think it better represents the possibilities. -- 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/834#issuecomment-464740675
Received on Monday, 18 February 2019 13:58:27 UTC