You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
HTML <iframe>: allow attribute needs stand-alone topic #32188
So the proposal is to create a stand-alone document for the allow attribute, pulling in the information from the Permissions-Policy document linked above. The Permissions-Policy document then might have a reduced set of information and a cross link.
Hi @hamishwillee,
I was planning to work on this issue, but I noticed that since it was opened, HTMLIFrameElement.allow was added in PR #31979.
Currently we have:
HTMLIFrameElement.allow documenting the DOM property.
The <iframe> element page with a brief description of the allow attribute.
The Permissions-Policy page containing the more detailed iframes section.
Before I start implementing anything, could you clarify the intended direction for this issue?
Should this issue still result in a separate page specifically for the HTML allow attribute, or would expanding the existing HTMLIFrameElement.allow page and updating the cross-links be the preferred approach?
When this issue was created the thinking was to create a link from the <iframe> doc allow attribute to permission policy docs (done) and then later create the dedicated doc proposed in this issue. Now I don't see it as necessary to do so: the link takes you to the right place. None of the other attributes have dedicated pages and much of what would be said is duplication.
When this issue was created the thinking was to create a link from the <iframe> doc allow attribute to permission policy docs (done) and then later create the dedicated doc proposed in this issue. Now I don't see it as necessary to do so: the link takes you to the right place. None of the other attributes have dedicated pages and much of what would be said is duplication.
So I don't think this is needed.
Closing. Thanks for bringing to my attention.
There are a lot of issues left open i will look over them also and help you maintain the issues.
Activity
BHUVANSH855 commentedon Jun 25, 2026
Hi @hamishwillee,
I was planning to work on this issue, but I noticed that since it was opened,
HTMLIFrameElement.allowwas added in PR #31979.Currently we have:
HTMLIFrameElement.allowdocumenting the DOM property.<iframe>element page with a brief description of theallowattribute.Permissions-Policypage containing the more detailediframessection.Before I start implementing anything, could you clarify the intended direction for this issue?
Should this issue still result in a separate page specifically for the HTML
allowattribute, or would expanding the existingHTMLIFrameElement.allowpage and updating the cross-links be the preferred approach?Thanks!
hamishwillee commentedon Jul 28, 2026
Thanks @BHUVANSH855
When this issue was created the thinking was to create a link from the
<iframe>doc allow attribute to permission policy docs (done) and then later create the dedicated doc proposed in this issue. Now I don't see it as necessary to do so: the link takes you to the right place. None of the other attributes have dedicated pages and much of what would be said is duplication.So I don't think this is needed.
Closing. Thanks for bringing to my attention.
BHUVANSH855 commentedon Jul 28, 2026
There are a lot of issues left open i will look over them also and help you maintain the issues.