-
Notifications
You must be signed in to change notification settings - Fork 80
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
Resource hint: check directives explicitly #637
base: main
Are you sure you want to change the base?
Conversation
Apparently the previous wording was a no-op. Instead of calling the pre-request check, checking the resource list for the directives that have that as a value. Closes w3c#633
|
||
then continue. | ||
|
||
1. Assert: |directive|'s <a for="directive">value</a> is a <a>source list</a>. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I guess this is not always true. For script-src
there can be nonces and hashes and keywords.
|
||
then continue. | ||
|
||
1. Assert: |directive|'s <a for="directive">value</a> is a <a>source list</a>. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should these and subsequent items in this list be incremented? Right now, they’re all numbered '1.' Was that intentional?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
FWIW, I think that's usually intentional so you don't have to renumber when you add or remove steps. (The output won't contain these numbers.)
Apparently the previous wording was a no-op.
Instead of calling the pre-request check, checking the resource list for the directives that have that as a value.
Closes #633