Skip to content

websites.thirdPartyCookiesAllowed can provide misleading information to developers #821

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

Open
aselya opened this issue May 5, 2025 · 0 comments
Labels
needs-triage: chrome Chrome needs to assess this issue for the first time needs-triage: firefox Firefox needs to assess this issue for the first time needs-triage: safari Safari needs to assess this issue for the first time

Comments

@aselya
Copy link
Contributor

aselya commented May 5, 2025

Mechanisms such as Storage Access API, allow individual frames to gain access to third-party cookies even when the global browser settings indicate that third-party cookies should be blocked. Since the existing privacy.websites.thirdPartyCookiesAllowed() API only provides insight into browser level settings, the return from the API can be misleading about the state of an individual frame.

Bug for additional context: crbug.com/415774014

@github-actions github-actions bot added needs-triage: chrome Chrome needs to assess this issue for the first time needs-triage: firefox Firefox needs to assess this issue for the first time needs-triage: safari Safari needs to assess this issue for the first time labels May 5, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs-triage: chrome Chrome needs to assess this issue for the first time needs-triage: firefox Firefox needs to assess this issue for the first time needs-triage: safari Safari needs to assess this issue for the first time
Projects
None yet
Development

No branches or pull requests

1 participant