[TAG] Confusion over extending policy into child frames

[triblondon]

From TAG review

Under the default allowlists header, the phrase "The feature is allowed at the top level by default, and when allowed, is allowed by default to documents in child frames." is rather confusing, and suggests to us that perhaps the allow attribute is required in order to extend a feature-policy defined in the header, into child frames (which doesn't make a lot of sense because in that case there'd be no reason to have multiple origins listed in the header policy). Perhaps this is a hangover from a previous version of the spec in which there was a disable attribute as well as the enable (now allow) one?

[clelland]

Ew, that is confusing. Thanks for pointing it out, I'll rewrite that to hopefully make more sense.