SaaSHub helps you find the best software and product alternatives Learn more →
Webappsec-permissions-policy Alternatives
Similar projects and alternatives to webappsec-permissions-policy
-
-
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
-
contain-google
[Looking for maintainer] - Google Container isolates your Google activity from the rest of your web activity in order to prevent Google from tracking you outside of the Google website via third party cookies.
-
-
contain-facebook
Facebook Container isolates your Facebook activity from the rest of your web activity in order to prevent Facebook from tracking you outside of the Facebook website via third party cookies.
-
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
-
webappsec-feature-policy
Discontinued A mechanism to selectively enable and disable browser features and APIs [Moved to: https://github.com/w3c/webappsec-permissions-policy]
NOTE:
The number of mentions on this list indicates mentions on common posts plus user suggested alternatives.
Hence, a higher number means a better webappsec-permissions-policy alternative or higher similarity.
webappsec-permissions-policy reviews and mentions
Posts with mentions or reviews of webappsec-permissions-policy.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-11-24.
-
Smart Move, Google
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 didn't find an explicit example for what happens if the iframe domain already got permission previously.
As you say the UI for requesting in this case would be weird, and this seems like a big security hole to me, but I can’t see a bit of the spec that explicitly forbids (though I only scanned the doc.)
-
Amazon is blocking Google’s FLoC
there is apparently no way to 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?!
-
Optimise your site - Addressing recommendations from securityheaders.com
This took a fair bit of investigation. I'm not convinced that it's the most well-documented header, in terms of the properties that you can set. Effectively, this is a list of values that determine which permissions are allowed for this website. Given I don't need access to location, camera, microphone or accelerometer. I did have issues finding consistent documentation on this one, so ended up having to combine the Feature-Policy documentation from MDN as well as the permissions policy examples from w3c.
-
User-Agent Client-Hints, take 2
Since Chrome v84 the Chrome team has had a few set backs which has resulted in some changes. In addition, the feature policy header, for delegating the client hints to third parties, has changed name to Permissions-Policy.
-
A note from our sponsor - SaaSHub
www.saashub.com | 3 May 2024
Stats
Basic webappsec-permissions-policy repo stats
5
391
6.9
25 days ago
w3c/webappsec-permissions-policy is an open source project licensed under GNU General Public License v3.0 or later which is an OSI approved license.
The primary programming language of webappsec-permissions-policy is Bikeshed.
Sponsored
SaaSHub - Software Alternatives and Reviews
SaaSHub helps you find the best software and product alternatives
www.saashub.com