fenced-frame
fenced-frame copied to clipboard
Network restrictions
What will be the implications for 3rd party verification vendors if networking will be disabled by default? Are you planning on potentially opening up to integrations with such vendors so information like viewability / IVT could be sent out of a fenced iframe?
There are plans to have a channel from the fenced frames to the worklets doing reporting. That will hopefully address many use cases including spam detection. There will be more details published in a subsequent explainer document we are working on.
Hi, it's me again 2 years later. I am trying to find an answer to a following question but I have a hard time finding it:
Will script inside fenced iframe be allowed to make an api call to a server?
We've created a test page with fenced iframe element and we can see that outbound network communication is allowed, but it is only a test page and we're not sure if this still will be the case in the future.
I understand the reporting worklets will be one way to get the data out, but will it be THE ONLY way in the future?
Hi @robert-fiedor would you kindly please add your company affiliation in your GitHub profile? We have been working with a few companies in the ad verification space and we're actually tracking this very reasonable feedback and making sure it's accounted in our Fenced Frames plans. If you work for one of the companies we're actively engaging then I can bring you in to those discussions so you have other channels for feedback beyond Github. Thanks!