Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

document.suborigin or something should allow JS to detect if in suborigin #35

Open
devd opened this issue May 9, 2016 · 7 comments
Open
Milestone

Comments

@devd
Copy link
Contributor

devd commented May 9, 2016

No description provided.

@annevk
Copy link
Member

annevk commented May 9, 2016

Note that apart from document.origin, we also have self.origin these days. They are subtly different in edge cases.

@devd
Copy link
Contributor Author

devd commented May 9, 2016

ohh .. didn't know that. do you have a link explaining this?

On 9 May 2016 at 10:23, Anne van Kesteren notifications@github.com wrote:

Note that apart from document.origin, we also have self.origin these days.
They are subtly different in edge cases.


You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
#35 (comment)

@annevk
Copy link
Member

annevk commented May 10, 2016

whatwg/html#951 (comment) is the best I have thus far.

@joelweinberger joelweinberger added v1 and removed v1 labels Sep 30, 2016
@joelweinberger joelweinberger modified the milestone: v1 Sep 30, 2016
@devd devd changed the title document.suborigin or something should make allow JS to detect if in suborigin document.suborigin or something should allow JS to detect if in suborigin May 13, 2017
@devd
Copy link
Contributor Author

devd commented May 13, 2017

@jeisinger thoughts on this?

@jeisinger
Copy link
Member

I'd propose to go with self.suborigin to mirror self.origin. As @annevk pointed out, document.origin is deprecated

@devd
Copy link
Contributor Author

devd commented May 15, 2017

We could also go with self.origin returning the ExtendedOrigin object similar to what we did in postMessage. That seems cleaner IMO.

@annevk
Copy link
Member

annevk commented Sep 27, 2017

That kind of generalization would work better for Origin Isolation too (I think we'd want to expose that to JavaScript, though I don't think we want to change postMessage() for it).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants