Document Policy

[clelland]

Introduction

This was originally proposed on Discourse, but this seems to be the new place for proposals.

Document Policy is a configuration mechanism for the web platform, allowing site authors (for instance) to enable or disable the use of platform APIs, improve their performance by setting thresholds for the sizes or efficiency of images, or sandbox individual frames.

It has split from Feature Policy, as a means of configuring features other than permissions, and so currently lives in a W3C WebAppSec WG repo. The spec is already in progress there, but the consensus of the WG is that it should be incubated at WICG while it is completed, and while we gather implementer interest.

Read the complete Explainer or the spec

Document Policy is under review by TAG.
It has been partially shipped in Chrome to support the "Scroll-to-text-fragment" feature.

Feedback (Choose One)

Please provide all feedback below.

[clelland]

This move was originally suggested by Mozilla folks (w3c/webappsec-permissions-policy#411 most recently, but it had been discussed previously).

Moving to WICG was also discussed in WebAppSec WG meetings in May (minutes) and then again in November (minutes) because I had forgotten about it :)

[yoavweiss]

Seems like there's enough support for the move to WICG. Do you have a repo you want to move, or should we create a new one?

[clelland]

It currently lives within the w3c/webappsec-permissions-policy repo, as it split off of that spec, but we shouldn't move the whole repo. Probably best to create a new one, and migrate the relevant issues.

[yoavweiss]

I've spun up https://github.com/WICG/document-policy and gave you access.

Happy incubating!

[clelland]

Thanks!

[yoavweiss]

Let's leave this open to keep track of the proposal through its lifecycle (so, until it graduates to a WG)

[clelland]

SGTM. (I thought this was more a "proposal to open a new repo" rather than "proposal for a new API")