Re: [w3ctag/spec-reviews] PaymentRequest.canMakeActivePayment() (#146)

Picked up at Boston F2F.

Seems that the current thinking on this is that the method should compute the intersection of the payment methods accepted by the website and the methods offered by the user, and return true if the result is non-empty set.  However, to defend against fishing expeditions, there needs to be some constraint on how many times this method can be called with different params.  @slightlyoff determined that in Chrome, the result is cached for 30 mins for an origin, so if you make a second invocation with different params you will get the previously cached result (which may be - somewhat intentionally - wrong for the new invocation)

Resolved that @dbaron would review the spec and we'll follow up on next week's call.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/spec-reviews/issues/146#issuecomment-278791586