2 ms·

It's specified here: https://www.w3.org/TR/permissions-policy-1/#policy-controlled-feature https://www.w3.org/TR/permissions-policy-1/#policy-controlle... Ther

It's specified here: https://www.w3.org/TR/permissions-policy-1/#policy-controlled-feature https://www.w3.org/TR/permissions-policy-1/#policy-controlle... There is a non-exhaustive list of features/APIs here: https://github.com/w3c/webappsec-feature-policy/blob/master/features.md https://github.com/w3c/webappsec-feature-policy/blob/master/... Each feature takes an allowlist, specifying which, if any, origins can use the feature.

stock_toaster 5y ago
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/189 https://github.com/w3c/webappsec-permissions-policy/issues/1... What is happening in w3c?!
- robin_reala 5y ago
  A cynical view would be that Google paid large sums to advertise Chrome on prime time TV while sideloading it with Flash and Java installs, which lead to an outsize user base, which lead to outsize influence at W3C on specifications.