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

Move location.fragmentDirective to document.fragmentDirective #130

Closed
bokand opened this issue Aug 6, 2020 · 1 comment · Fixed by #134
Closed

Move location.fragmentDirective to document.fragmentDirective #130

bokand opened this issue Aug 6, 2020 · 1 comment · Fixed by #134

Comments

@bokand
Copy link
Collaborator

bokand commented Aug 6, 2020

See https://crbug.com/1057795 and whatwg/html#5523

Basically, window.location is special in all kinds of ways and is spec'd to represent the URL of its document's browsing context's active document, not the Document itself. If we start adding things to fragmentDirective this would allow cross-origin access to values which is bad.

Moving fragmentDirective to live on document seems like a more safe and natural place for it.

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