Re: [w3c/webpayments-payment-apps-api] Change from clients.openWindow to event.openWindow. (#106)

tommythorsen commented on this pull request.



> @@ -964,9 +970,15 @@
       opens a window. For subsequent payments in the same session, the payment handler (through configuration) performs its duties without opening a window or requiring user interaction.</li>
   </ul>
 
-  <p class="issue">See <a href="https://github.com/w3c/webpayments-payment-apps-api/issues/97">issue 97</a> for discussion about opening window in a way that is consistent with payment flow and not confusing to the user. For example, there is consensus that in a desktop environment, a payment handler should <em>not</em> open a window in a new browser tab, as this is too dissociated from the checkout context.</p>
-  
-  <p>User agents SHOULD display the origin of a running payment handler to the user.</p>
+  <p>A payment handler that requires visual display and user interaction, may call <code>PaymentRequestEvent.openWindow()</code>.
+    Since user agents know that this method is connected to the payment request event, they SHOULD render the window in a way that is consistent with the flow and not confusing to the user.</p>
+
+  <p>The resulting window client is bound to the tab/window that initiated the <a>payment request</a>.
+    A single <a>payment handler</a> SHOULD NOT be allowed to open more than one client window using this method.

I'm working on this. Aiming to update this PR with an algorithm for openWindow tomorrow.

-- 
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/webpayments-payment-apps-api/pull/106#discussion_r106178996