Re: [w3c/browser-payment-api] canMakePayment() might be in the wrong place? (#403)

Ok, np. Wanted to check as I wasn't sure about it shipping. 

> On 21 Jan 2017, at 1:49 am, Rouslan Solomakhin <notifications@github.com> wrote:
> 
> I would prefer that we keep that API as-is. I view spinning up an instance of PaymentRequest as an advantage, not a detriment, because this warmed up instance of PaymentRequest will be able to respond to .show() call much faster, now that it has queried the installed payment apps.
> 
> By the way, Chrome has shipped .canMakePayment() in M56, which is currently in beta, soon to be stable.
> 
> —
> You are receiving this because you authored the thread.
> Reply to this email directly, view it on GitHub, or mute the 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/browser-payment-api/issues/403#issuecomment-274094640

Received on Friday, 20 January 2017 15:10:12 UTC