Support iframe enable and disable attributes in Feature Policy |
||||||
Issue descriptionDocuments should be able to specify 'enable' and 'disable' attributes in <iframe> tags to enable and disable specific features in child frames. These should follow the algorithms given in the spec, or (until merged) in https://docs.google.com/document/d/1saEBLE6d-qmMxao8Aw6A06oSP3yKdUG7lqMWBYlzEgg/
,
Nov 4 2016
@iclelland Could you fill "Components" field and avoid "Blink"? Thanks! (commenting as a part of my blink bug triage sheriff duty)
,
Nov 6 2016
I think SecurityFeature is closest though it's not strictly for security?
,
Jan 3 2017
,
Jan 3 2017
,
Mar 21 2017
,
Mar 21 2017
,
May 26 2017
Isn't this same as iframe allow attribute? Are we still doing disable attribute?
,
May 26 2017
Currently not, although the full policy attribute is yet to be specced. This could still re-emerge as the best solution (though I think it's unlikely)
,
Jul 24 2017
I think iclelland/lunalu basically implemented this now. |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by iclell...@chromium.org
, Nov 2 2016Status: Assigned (was: Available)