Re: [w3c/payment-request] Some clarifications with Payment Request API (#774) from Marcos Cáceres on 2018-09-13 (public-webpayments-specs@w3.org from September 2018)

From: Marcos Cáceres <notifications@github.com>
Date: Wed, 12 Sep 2018 23:22:47 -0700
To: w3c/payment-request <payment-request@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <w3c/payment-request/issues/774/420897057@github.com>

@agektmr I'm worried about having multiple sources of truth about "API readiness". We already have caniuse, the MDN's data, and the (canonical) [implementation report](https://w3c.github.io/test-results/payment-request/all.html).

The implementation report is not great at the moment... but the data from it should be the source of truth, and it represents the most accurate representation of conformance/readiness.  

If we want to build a more developer friendly "IsWebPaymentsReady", we should base it off the data that powers the implementation report

-- 
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/774#issuecomment-420897057

Received on Thursday, 13 September 2018 06:23:09 UTC