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

domenic 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

> Both of these would theoretically show the payment sheet in the popup:

Yeah, that's right!

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

I don't quite understand what you mean here.

> I've put up an initial set that use just an iframe:

I'll take a look, but iframes are not as good a test here, as they aren't top-level browsing contexts. The payment-relevant browsing context of a PaymentRequest created inside an iframe is its parent browsing context. Popups are special because they are top-level; they don't have a parent, just an opener.

-- 
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_r237633475