w3c/webappsec-permissions-policy
View on GitHub ↗ ★ 432 Bikeshed
A mechanism to selectively enable and disable browser features and APIs
4 mentions on Hacker News by 4 people: 0 stories, 4 comments · first 2021-06-16 · latest 2025-01-29
20082026
-
…of how the web is built or whether the page they are navigating consists of different components ( https://github.com/w3c/webappsec-permissions-policy/issues/5... ).
comment by bubububu · 2025-01-29 · in Browser Permissions -
Thanks for the docs. The examples (2 & 3, https://github.com/w3c/webappsec-permissions-policy/blob/mai... ) seem to me to say that search.google.com can’t grant location permissions to an iframe if the parent was forbidden them, but I…
comment by theptip · 2022-11-24 · in maps.google.com now redirects to google.com/maps -
…from the iframe (might confuse people), but if you already have them, it ought to be fine. [0] https://github.com/w3c/webappsec-permissions-policy/blob/mai...
comment by luckylion · 2022-11-24 · in maps.google.com now redirects to google.com/maps -
…define a default disable either, so to turn off all the random features, the header becomes huge. https://github.com/w3c/webappsec-permissions-policy/issues/1... What is happening in w3c?!
comment by stock_toaster · 2021-06-16 · in Amazon is blocking Google’s FLoC