Re: [w3c/payment-handler] Define requestPermission() behavior. (#180)

rsolomakhin commented on this pull request.



>            </p>
+          <ol>
+            <li>Let <var>p</var> be a new promise.
+            </li>
+            <li>Run the following steps in parallel:
+              <ol>
+                <li>Let <var>permission</var> be the result of running
+                <a data-cite="!permissions#dfn-retrieve-the-permission-state">
+                  retrieve the permission state algorithm</a> of the permission
+                  associated with <a>payment handler</a>.
+                </li>
+                <li>If <var>permission</var> is "prompt", ask the user whether
+                allowing adding new payment instruments for the <a data-cite=
+                "!HTML#current-settings-object">current settings object</a>'s
+                origin is acceptable. If it is, set <var>permission</var> to
+                "granted", and "denied" otherwise.

Your [implementation](https://codereview.chromium.org/2946013002/diff/1/third_party/WebKit/Source/modules/payments/PaymentManager.cpp) can also resolve `p` with `"default"`. When would that happen?

-- 
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-handler/pull/180#pullrequestreview-45444316