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.

Sign up for GitHub

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

Jump to bottom

Should we replace browsing contexts with navigables? #579

Closed
antosart opened this issue Nov 25, 2022 · 2 comments · Fixed by #580
Closed

Should we replace browsing contexts with navigables? #579

antosart opened this issue Nov 25, 2022 · 2 comments · Fixed by #580

Comments

@antosart
Copy link
Member

The spec uses browsing contexts for the frame-ancestors check. In the html spec, navigables have been introduced. Should we replace browsing contexts with navigables? If so, we should pass a navigable instead of a browsing context as target in the https://w3c.github.io/webappsec-csp/#should-block-navigation-response algorithm.
@antosart
Copy link
Member Author

CC @domenic.

@antosart antosart mentioned this issue Nov 25, 2022
Merged
@domenic
Copy link
Contributor

domenic commented Nov 25, 2022

Yes, I think replacing all references to browsing contexts with the corresponding navigable terminology would be an improvement, since your spec isn't one of the few that wants to have different behaviors before and after BCG swaps.

Please let me know if I can help.

@antosart antosart mentioned this issue Nov 28, 2022
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Fix references to html after navigation and session history rewrite antosart/webappsec-csp
2 participants
@domenic @antosart