- From: Marcos Cáceres <notifications@github.com>
- Date: Wed, 10 May 2017 21:23:13 -0700
- To: w3c/browser-payment-api <browser-payment-api@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Thursday, 11 May 2017 04:24:11 UTC
marcoscaceres requested changes on this pull request. One small change. > @@ -623,6 +623,24 @@ <li>Let <var>request</var> be the <a>PaymentRequest</a> object on which the method is called. </li> + <li> + <p> + Optionally, if the <a>user agent</a> wishes to disallow the call + to <a>show()</a> to protect the user, then return a promise + rejected with a "<a>SecurityError</a>" <a>DOMException</a>. For + example, the <a>user agent</a> may require the call to be + <a>triggered by user activation</a>, or may limit the rate at + which a page can call <a>show()</a>, as described in the the + <a href="#privacy">privacy considerations</a> section. + </p> + <p> This should be a Note, stating that: "During the Candidate Recommendation phase, implementations are expected to experiment in this area..." And concluding with: "If interoperable behavior emerges amongst user agents, then that behavior will be standardized here before progressing the specification along the W3C Recommendation Track." -- 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/512#pullrequestreview-37480956
Received on Thursday, 11 May 2017 04:24:11 UTC