michaelkleber
commented
1 week ago We are trying to understand detailed usage observation of Topics API, and seems even from Networking tab, there is a call sent and caught, within chrome://topics-internals/ there is no observer recorded, is this expected?
When using the HTTP header mechanism to interact with the Topics API, the topics are sent in the Sec-Browsing-Topics request header, but they are only observed if the server replies with the Observe-Browsing-Topics: ?1 response header. See all the details in this part of the explainer.
A quick note is that as suggested we will add more details into our account to ensure there is no concern from your side, but if it is not required we would prefer it to be totally open-sourced eco-system:)
This repository is for the ongoing work to design a browser API, under the auspices of the W3C's Private Advertising Technology Community Group. Contributions to that effort are subject to the W3C Community Contributor License Agreement, an essential part of the protections that ensure acceptable licensing rights for the work that comes out of the web standards process. This is how you make something an open-source ecosystem.
If you don't want to identify yourself as part of an organization that has entered into that legal agreement, then we cannot let you contribute to this group's work. You can consider asking questions in our Privacy Sandbox Developer Support forum, if you're just looking for understanding and documentation, rather than contributing to ongoing design discussions.
Hi Topics API experts,
We are trying to understand detailed usage observation of Topics API, and seems even from Networking tab, there is a call sent and caught, within chrome://topics-internals/ there is no observer recorded, is this expected? thanks.
e.g:
A quick note is that as suggested we will add more details into our account to ensure there is no concern from your side, but if it is not required we would prefer it to be totally open-sourced eco-system:) thanks!