- From: Stephen McGruer <notifications@github.com>
- Date: Mon, 15 Nov 2021 13:43:42 -0800
- To: w3c/payment-request <payment-request@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Monday, 15 November 2021 21:43:54 UTC
Would it be useful to export a `dfn` here that can be pointed to by other specs, similarly to https://w3c.github.io/payment-request/#dfn-steps-to-check-if-a-payment-can-be-made (and respond, and change)? It's much easier to write other specs when you can say `The [=steps to check if a payment can be made=] for [=my new payment method=] are: ...`. (Also, I assume this change doesn't obsolete the `steps to check if a payment can be made` because technically handlers to methods are N:1, though in practice I think it is 1:1?) (Also also, reminder - `steps to check if a payment can be made` have *nothing* to do with canMakePayment, they're actually a check used inside of `show()` :D) -- 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/pull/976#issuecomment-969349406
Received on Monday, 15 November 2021 21:43:54 UTC