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

Should the policy-controlled feature definitions live in this spec, or in infrastructure? #2

Open
eeeps opened this issue Aug 5, 2020 · 2 comments
Open

Should the policy-controlled feature definitions live in this spec, or in infrastructure? #2

eeeps opened this issue Aug 5, 2020 · 2 comments

Comments

@eeeps
Copy link
Collaborator

eeeps commented Aug 5, 2020 •
edited

Currently they live here: https://wicg.github.io/client-hints-infrastructure/#policy-controlled-features

Seems kind of nice to wrap both the HTTP headers and policy-controlled-features all up in one spec, however I'm guessing having the registry in the infrastructure spec makes sense, for integration-with-Fetch reasons?
@eeeps eeeps changed the title Should the policy-controlled feature names live in this spec, or in infrastructure? Should the policy-controlled feature definitions live in this spec, or in infrastructure? Aug 5, 2020
@eeeps
Copy link
Collaborator Author

eeeps commented Aug 5, 2020

We should probably link to them in some normative section.

@eeeps
Copy link
Collaborator Author

eeeps commented Aug 12, 2020

related: WICG/ua-client-hints#123

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
No milestone
Development

No branches or pull requests
1 participant
@eeeps