Re: [w3c/browser-payment-api] Detecting Payment Method Availability (#316)

maheshkk commented on this pull request.



>              <code>false</code>, otherwise resolve <var>acceptPromise</var> with <code>true</code>.
           </li>
           <li>
-            Cache the response in <var>cachedResponse</var> and set <var>cacheInvalidateTimer</var> to certain <a>DateTime</a> for the <var>topLevelDomain</var>.
+            Cache the response in <var>cachedResponse</var> and set <var>canMakePaymentQuotaReached</var> to 
+            to true.
+          </li>
+          <li> 
+            In addition, implementations may choose to implement a timeout to reset 
+            <var>canMakePaymentQuotaReached</var> for the <var>topLevelOrigin</var>.

There are two points where quota reserts, .
1. Quota resets after the session ends (window closed/navigate away from the page)
2. Optional : reset after certain timeout. 

I believe your concern is to remove the optional part from second option. Say if some implementors choose to set timeout to zero then it has same effect as keeping the check optional at the moment. Then I wonder why enforce the step with "Must" or "should"?

-- 
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/pull/316