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

Delivery section should address new/unrecognized features and directive members #47

Closed
ddorwin opened this issue Nov 24, 2016 · 1 comment
Closed

Delivery section should address new/unrecognized features and directive members #47

ddorwin opened this issue Nov 24, 2016 · 1 comment
Milestone
v1

Comments

@ddorwin
Copy link

ddorwin commented Nov 24, 2016

https://wicg.github.io/feature-policy/#feature-policy-http-header-field says:

When the user agent receives a Feature-Policy header field, it MUST process and enforce the serialized policy as described in 5.1 Integration with HTML.

Related to #44, including the current directive definition text, this section should acknowledge that clients may not recognize all features or directives members and thus may not process or enforce them as the server intends. In other words, while user agents should do the correct thing for their users, there is no mechanism for the server to guarantee that they are being applied. (In a compliant implementation, the feature policy advertised by each fetch could be used to check.)


"The meta element" section should have similar MUST language and acknowledgement.
@clelland clelland self-assigned this Apr 5, 2017
@clelland clelland added this to the v1 milestone Apr 5, 2017
clelland added a commit to clelland/feature-policy that referenced this issue Apr 5, 2017
@clelland
Explicitly note that not all features may be recognized
057c41d 
Adds a note that, even though the header parsing text indicates that
user agents MUST process the header field, that not every UA will
recognize every feature, and so the effective policy may not be
interpreted exactly as the origin server intended.

Fixes w3c#47
@clelland
Copy link
Collaborator

clelland commented Apr 5, 2017

@ddorwin, does the text in that update make sense to you?

The meta element section has been removed from the spec, pending resolving #55

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
v1
Development

No branches or pull requests
2 participants
@clelland @ddorwin