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

Update: Content Security Policy #1446

Closed
tbroyer opened this issue Jul 8, 2024 · 4 comments
Closed

Update: Content Security Policy #1446

tbroyer opened this issue Jul 8, 2024 · 4 comments
Labels
ACK_OBTAINED Issue acknowledged from core team so work can be done to fix it. HELP_WANTED Issue for which help is wanted to do the job. UPDATE_CS Issue about the update/refactoring of a existing cheat sheet.

Comments

@tbroyer
Copy link
Contributor

tbroyer commented Jul 8, 2024

What is missing or needs to be updated?

The navigate-to directive has been removed from the CSP3 spec nearly 2 years ago (w3c/webappsec-csp#564)

How should this be resolved?

Remove mention of navigate-to
@tbroyer tbroyer added ACK_WAITING Issue waiting acknowledgement from core team before to start the work to fix it. HELP_WANTED Issue for which help is wanted to do the job. UPDATE_CS Issue about the update/refactoring of a existing cheat sheet. labels Jul 8, 2024
@mackowski mackowski added ACK_OBTAINED Issue acknowledged from core team so work can be done to fix it. and removed ACK_WAITING Issue waiting acknowledgement from core team before to start the work to fix it. labels Jul 8, 2024
@mackowski
Copy link
Collaborator

@tbroyer good issue, thanks! Do you want to make a small PR for that?

@tbroyer tbroyer mentioned this issue Jul 8, 2024
Merged
8 tasks
@eligrey
Copy link

eligrey commented Jul 10, 2024

This could be replaced with a mention that navigation can be controlled via other APIs, such as the Navigation API.

@Jeymz
Copy link
Contributor

Jeymz commented Aug 7, 2024

I don't see any mention of the navigate-to directive within the Content_Security_Policy_Cheat_Sheet. Can this be closed?

@szh
Copy link
Collaborator

szh commented Aug 7, 2024

Yes, this was completed in #1447. Thanks!

@szh szh closed this as completed Aug 7, 2024
@szh szh mentioned this issue Aug 7, 2024
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
ACK_OBTAINED Issue acknowledged from core team so work can be done to fix it. HELP_WANTED Issue for which help is wanted to do the job. UPDATE_CS Issue about the update/refactoring of a existing cheat sheet.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@eligrey @tbroyer @szh @Jeymz @mackowski