Re: [w3c/payment-request] Spec is silent on its role in facilitating arbitrary communication between top level contexts (#936) from Samuel Weiler on 2021-01-25 (public-webpayments-specs@w3.org from January 2021)

From: Samuel Weiler <notifications@github.com>
Date: Mon, 25 Jan 2021 10:32:31 -0800
To: w3c/payment-request <payment-request@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <w3c/payment-request/issues/936/767023201@github.com>

It seems like we should pointing at [this solution](https://github.com/w3c/payment-handler/issues/351#issuecomment-566642121) which I hope has been documented somewhere in the Payment Handler API.  

Maybe I'm missing a level of abstraction - do we expect the payment request API to point at anything other than **THE** payment handler PI?  If not, then why not point to the concrete fix?

-- 
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/936#issuecomment-767023201

Received on Monday, 25 January 2021 18:32:44 UTC