Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fenced Frame API for FLEDGE to check if <fencedframe> can load #321

Open
blu25 opened this issue Jun 28, 2022 · 0 comments
Open

Fenced Frame API for FLEDGE to check if <fencedframe> can load #321

blu25 opened this issue Jun 28, 2022 · 0 comments
Labels
Non-breaking Feature Request Feature request for functionality unlikely to break backwards compatibility

Comments

@blu25
Copy link
Contributor

blu25 commented Jun 28, 2022

The ad auctioning process in FLEDGE is an expensive process. Fenced frames have restrictions for what conditions need to be in place for one to load. If a fenced frame will not be able to load in the current context, it doesn't make sense for ad auctioning to take place only for the ad to not be able to be displayed in the page.
The API could exist as a static and synchronous method of the HTMLFencedFrameElement class, which would check if adding a new fenced frame inside the current execution context's frame would be allowed or not. It would be invoked by calling:
HTMLFencedFrameElement.canLoadOpaqueURL();
which would return either true or false.

See the design document for implementation details.

@JensenPaul JensenPaul added the Non-breaking Feature Request Feature request for functionality unlikely to break backwards compatibility label Jun 23, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Non-breaking Feature Request Feature request for functionality unlikely to break backwards compatibility
Projects
None yet
Development

No branches or pull requests

2 participants