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

Since Chrome 126: joinAdInterestGroup function unavailable with #enable-fenced-frames #383

Open
ccharnay67 opened this issue Jun 24, 2024 · 1 comment

Comments

@ccharnay67
Copy link

Hello,

We noticed recently on Chrome stable an beta that joinAdInterestGroup (and probably other APIs) were sometimes not available in the browser.

I noticed that this happened in Chrome 126 whenever the #enable-fenced-frames is modified, there is an issue when it is Enabled or Disabled, but not when it is "Default". I am wondering if this could be related to the removal of the #privacy-sandbox-ads-apis flag, since the documentation for #enable-fenced-frames states "This requires #privacy-sandbox-ads-apis to also be enabled."

Enabling #temporary-unexpire-flags-m125 and #privacy-sandbox-ads-apis flags solves the issue, but this sounds like a bug.

On Chrome Beta (128), I notice the API is also not available, no matter the state of the flags.

Can you please have a look?

Thank you in advance

@ccharnay67
Copy link
Author

I should add that now, on Chrome Beta (128.0.6559.0), the API is available when #enable-fenced-frames is either Enabled or Disabled, but not when it's set to Default, which is exactly the opposite from what I see in Chrome 126.0.6478.127, so it is a bit confusing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant