Re: [w3c/payment-request] Attach 'payment request is showing boolean' to top-level browsing context (#811)

marcoscaceres commented on this pull request.



> @@ -935,9 +934,9 @@ <h2>
           then return <a>a promise rejected with</a> an
           "<a>InvalidStateError</a>" <a>DOMException</a>.
           </li>
-          <li>If the <a>user agent</a>'s <a>payment request is showing</a>
-          boolean is true, then return <a>a promise rejected with</a> an
-          "<a>AbortError</a>" <a>DOMException</a>.
+          <li>If the <a>top-level browsing context</a>'s <a>payment request is

> And then could go from popup.opener, and show a payment sheet in the opener from the popup.

@domenic, imagine the following situation:

```JS
// this is actually a new browser tab...
const popupTab = window.open("tab.html");

// in which tab does the sheet show? In the popup tab or in opener tab? 
await new popupTab.PaymentRequest(method, details).show();
```

I guess "implementation detail"... 

Similarly, consider this one (little window):

```JS
// We make a little window... imagine, without toolbars, etc.
const popupWindow = window.open("window.html", "width=100,height=100,...");

// in which window does the sheet show? In the little window or in opener? 
await new popupWindow.PaymentRequest(method, details).show();
```

Similarly, I guess "implementation detail"?... don't think we can do much in the spec, but just wanted to point this out.  


-- 
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-request/pull/811#discussion_r246667400