Re: [w3c/webpayments-payment-apps-api] What is matching and display behavior for various scenarios of recommended apps, enabled apps, non-enabled apps, etc.? (#38) from ianbjacobs on 2017-01-06 (public-webpayments-specs@w3.org from January 2017)

From: ianbjacobs <notifications@github.com>
Date: Fri, 06 Jan 2017 06:39:25 -0800
To: w3c/webpayments-payment-apps-api <webpayments-payment-apps-api@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <w3c/webpayments-payment-apps-api/issues/38/270915848@github.com>

I am closing this issue based on how payment request API has evolved (e.g., canMakePayment)
and also that we do have some UI requirements in the specification (not detailed instructions, but requirements for any display solution). We are also in ongoing discussions on recommended payment app interactions on a separate thread.


-- 
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/webpayments-payment-apps-api/issues/38#issuecomment-270915848

Received on Friday, 6 January 2017 14:40:22 UTC