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.

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

Support for Permissions-Policy modifier #321

Open
ghost opened this issue Nov 3, 2023 · 0 comments
Open

Support for Permissions-Policy modifier #321

ghost opened this issue Nov 3, 2023 · 0 comments

Comments

@ghost
Copy link

ghost commented Nov 3, 2023

The HTTP Permissions-Policy header provides a mechanism to allow and deny the use of browser features in a document or within any <iframe> elements in the document.

References:
https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Permissions-Policy
https://adguard.com/kb/general/ad-filtering/create-own-filters/#permissions-modifier
https://docs.w3cub.com/http/headers/feature-policy#directives
https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Permissions-Policy
https://github.com/gorhill/uBlock/wiki/Static-filter-syntax#permissions

uBlock added in their lists:

!#if env_chromium
*$permissions=browsing-topics=(),from=~localhost
*$permissions=idle-detection=(),from=~localhost
*$permissions=join-ad-interest-group=(),from=~localhost
*$permissions=run-ad-auction=(),from=~localhost
*$permissions=attribution-reporting=(),from=~localhost
!#endif

They are similar to CSP in the way they work, and while they might be less useful than CSP, it would be good if Brave also supported this modifier, not only for feature parity with uBlock lists, but also since they might be useful to have in some cases.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

0 participants