Skip to content

The initiator/destination/CSP table is not exhaustive when it comes t… #654

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

Merged
merged 2 commits into from
Jan 5, 2018

Conversation

annevk
Copy link
Member

@annevk annevk commented Jan 5, 2018

…o features

Fixes #652.


Preview | Diff

@annevk annevk requested a review from wanderview January 5, 2018 14:24
@annevk
Copy link
Member Author

annevk commented Jan 5, 2018

(I guess when landing I should try to shorten the commit title.)

fetch.bs Outdated
@@ -830,7 +830,8 @@ not always relevant and might require different behavior.

<div class=note>
<p>The following table illustrates the relationship between a <a for=/>request</a>'s
<a for=request>initiator</a>, <a for=request>destination</a>, CSP directives, and features.
<a for=request>initiator</a>, <a for=request>destination</a>, CSP directives, and features. It is
not exhaustive with respect to features. Features need to have the relevant values defined locally.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe s/locally/in their respective specifications/?

@annevk annevk merged commit a1d387c into master Jan 5, 2018
@annevk annevk deleted the annevk/destination-table-clarification branch January 5, 2018 15:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants