Handle a null request in init document csp algorithm #372
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
ccing @annevk as he reviewd whatwg/html#4190 (review) |
|
Fixes #364 |
andypaicu
force-pushed
the
init-doc-null-request
branch
from
6830b66
to
71aa991
Compare
andypaicu
force-pushed
the
init-doc-null-request
branch
from
71aa991
to
2708de1
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
https://w3c.github.io/webappsec-csp/#initialize-document-csp needs to handle a
nullrequest.The only relevant scenario is when the document is a
srcdoc iframebut it is handled in the html spec.Modified the
srcdoc iframenote to make it more clear and accurate.Preview | Diff