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

Feature-Policy is not set to a default "none" state. #24

Open

lewisgoddard opened this issue Aug 2, 2020 · 1 comment

Labels

💚 Priority: Low 🚧 Status: Blocked ✨ Type: Enhancement

Member

lewisgoddard commented Aug 2, 2020 •

edited

Loading

Is your feature request related to a problem? Please describe.
Currently, no Feature-Policy is specified.

Describe the solution you'd like
Specify Feature-Policy in an allow-nothing state.

Additional context
No current options w3c/webappsec-permissions-policy#189

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

The text was updated successfully, but these errors were encountered:

lewisgoddard added Status: Blocked labels

Member Author

lewisgoddard commented Oct 6, 2021

Still in a semi-draft state. https://github.com/w3c/webappsec-permissions-policy/blob/main/permissions-policy-explainer.md

lewisgoddard added 🚧 Status: Blocked 💚 Priority: Low ✨ Type: Enhancement and removed Status: Blocked labels

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment