vulns.co
/
GKData.io MCP and API Buy me a coffee

World Wide Web Consortium

Permissions Policy: inherited browser-feature authority across embedded documents

The Permissions Policy draft defines how a page limits browser features for itself and embedded documents. Embedded pages inherit restrictions and cannot re-enable a feature their parent disabled; defaults apply where no rule is declared. This work-in-progress specification complements sandboxing but does not replace user consent, application permissions or a full isolation design.

Open the referenceTechnical StandardReviewed 2026-10-03

How to use this reference

Editorial guidance: document which component owns each capability decision and distinguish intended delegation from effective restrictions. Keep browser-feature controls separate from application authorization and user consent in integration reviews.

Before reading

  • Browser origins, embedded documents and HTTP response headers

Context and limits

  • Work in progress, not a final Recommendation or deployed-compatibility guarantee. Listed authors are the draft's editors.
  • User agents need not support every feature. Frame-level observable policy omits child response policy and later navigation, so it does not establish the loaded document's effective access.
  • Complements iframe sandboxing; it is not a complete isolation model.

Sources

  1. Permissions PolicyWorld Wide Web Consortium · reviewed 2026-10-03

Record reviewed 2026-10-03. Snapshot af2809c308fc. Open the complete JSON contract.

Library synced 2026-11-18 · cases last reviewed 2026-10-05

af2809c308fc · JSON exports & schemas · CC BY 4.0 content / MIT software