Skip to content

Getting aggregation service config to browsers #129

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.

Sign up for GitHub

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

Jump to bottom
Closed
martinthomson opened this issue Apr 3, 2025 · 0 comments · Fixed by #149
Closed

Getting aggregation service config to browsers #129

martinthomson opened this issue Apr 3, 2025 · 0 comments · Fixed by #149
Labels
editor-ready Decisions have been made, can make a proposal

Comments

@martinthomson
Copy link
Member

We need to write down our expectations about the availability of aggregation service configuration.

Our goal is that the measureConversion API calls cannot fail. That means that browser need to have the configuration available always. Either the config ships with the browser code, or there is some way to hide the fact that the browser is fetching that configuration.
martinthomson added a commit that referenced this issue May 1, 2025
@martinthomson
Fingerprinting risk of unconfigured browsers
2610838 
Closes #129.
@martinthomson martinthomson mentioned this issue May 1, 2025
Merged
@martinthomson martinthomson added the editor-ready Decisions have been made, can make a proposal label May 16, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
editor-ready Decisions have been made, can make a proposal
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Fingerprinting risk of unconfigured browsers w3c/ppa
1 participant
@martinthomson