Re: [w3c/payment-handler] [WIP] showPaymentUI() method (#325)

romandev commented on this pull request.

To help your understanding, I have a plan to implement POC for this idea. Do you think that it's useful?

> @@ -1643,6 +1654,44 @@ <h2>
         <a>PaymentRequest</a>. A single <a>payment handler</a> SHOULD NOT be
         allowed to open more than one client window using this method.
       </p>
+      <section data-dfn-for="PaymentHandlerContainer" data-link-for=
+      "PaymentHandlerContainer">
+        <h2>
+          <dfn>PaymentHandlerContainer</dfn> interface
+        </h2>
+        <pre class="idl">
+        [SecureContxt, Exposed=Window]
+        interface PaymentHandlerContainer {
+          readonly attribute object? data;
+          void respondWith(PaymentHandlerResponse response);
+        };
+
+        partial interface Navigator {
+          [SecureContext, SameObject] readonly attribute PaymentHandlerContainer paymentHandler;

Okay, I agree with this. I'll update this soon.

> +        partial interface Navigator {
+          [SecureContext, SameObject] readonly attribute PaymentHandlerContainer paymentHandler;
+        };
+        </pre>
+        <section>
+          <h2>
+            <dfn>data</dfn> attribute
+          </h2>
+          <p>
+            The <a>data</a> attribute returns
+            <a>[[\paymentHandlerRequestData]]</a>.
+          </p>
+        </section>
+        <section>
+          <h2>
+            <dfn>respondWith()</dfn> method

This method simply passes the response data to SW thread. So, I thought that the method's explanation is enough.

-- 
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/325#pullrequestreview-159556320

Received on Thursday, 27 September 2018 17:33:42 UTC