[marcoscaceres]

Chrome shows that ~37% of sites tested are using document.featurePolicy:
https://chromestatus.com/metrics/feature/timeline/popularity/2511

We should consider switching this back.

Related web platform tests:
web-platform-tests/wpt#58463

---

Preview | Diff

[Copilot]

Pull request overview

Updates the Permissions Policy spec’s script introspection API surface to use the legacy FeaturePolicy naming (matching current web-compat usage like document.featurePolicy) instead of PermissionsPolicy.

Changes:

• Rename the script-facing policy object from PermissionsPolicy to FeaturePolicy in prose and examples.
• Update WebIDL to expose Document.featurePolicy / HTMLIFrameElement.featurePolicy returning FeaturePolicy.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[annevk]

Since this API does not have agreement and only one implementation I think it would be better to remove it.

[marcoscaceres]

Might be ok to remove it, but we would need to transplant it to the Web Compat spec.

[annevk]

Why? There's only one implementation and nobody else wants to implement it.

[marcoscaceres]

Ok, sure (and I agree), but we have the "37% of sites tested are using" it Chrome situation... this is a transitional path. This at least matches Chrome and we can then hopefully get agreement at TPAC to remove it and document the path to using permissions.query() instead.

It's the least bad option right now, IMO.

As a compromise, should we maybe add a note/issue that says that this is a Feature at Risk?

[annevk]

I don't see why that is a reason to keep it in the specification? Also page loads doesn't translate to websites.

[marcoscaceres]

I opened #600, which removes the API from the specification entirely, as @annevk suggested. We can discuss both options at TPAC.

[arichiv]

@miketaylr suggested the usage might go away as privacy sandbox APIs are retired, agree we should discuss at TPAC