Re: [w3c/webpayments-payment-apps-api] Extending invocation of payment apps with other techniques than HTTP (#10)

> Yes, except I don't think the intent is for it to be a background running process or be origin bound. So it will differ slightly.

Can you explain what you mean by it not being “origin bound“? Or is it explained already elsewhere?

Am I misunderstanding something, or are you suggesting there’s a proposal to somehow install a JavaScript file into a browser in such as way that it subsequently be can executed without being  bound to any origin?

JavaScript execution in browsers follows the same-origin policy, right? Any JavaScript is going to run under *some* single origin, and there’s (rightly) no way to install a JavaScript file into a browser in a way that enables it to be run from multiple origins.

-- 
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/issues/10#issuecomment-239723452