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

There's no reason to make fetch of about:blank same-origin for loads other than navigations and <object> #384

Closed
bzbarsky opened this issue Sep 13, 2016 · 3 comments

Comments

@bzbarsky
Copy link

bzbarsky commented Sep 13, 2016

I don't think it's required for web compat. Gecko only does this for navigations and <object> (things that can end up with a browsing context). Specifically, about:blank stylesheets are cross-origin in Gecko, and you can't XHR to about:blank in either Gecko or Blink (but can in WebKit, apparently).

@annevk
Copy link
Member

annevk commented Sep 14, 2016

@youennf what do you think?

Navigate is already always same-origin. <object> would require some special casing but that seems fine.

If we changed this we'd automatically fix #385 since all about URL fetching would just be cross-origin (unless it's the result of a navigation).

@youennf
Copy link
Collaborator

youennf commented Sep 14, 2016

I don't think XHR/fetch is working for about:blank in WebKit.
Sounds good to make consistent all about URLs.

@annevk
Copy link
Member

annevk commented Sep 14, 2016

Thanks.

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

No branches or pull requests

3 participants