Re: [w3c/payment-handler] topLevelOrigin is a weird name (#259)

> I don't think we've ever used "top level" in a public API before.

Innovation? ;-)

For a bit of context, we want to distinguish between the origin of the top-level context and that of the sub-iframe within that called `new PaymentRequest()`.  This can happen, for example, if `https://mom-and-pop-shop.com` embeds an iframe from `https://payment-processing-corp.com` in the checkout page. In this case, the `topLevelOrigin` is `https://mom-and-pop-shop.com` and the `paymentRequestOrigin` is `https://payment-processing-corp.com`.

-- 
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/issues/259#issuecomment-373736574

Received on Friday, 16 March 2018 14:49:28 UTC