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

document.browsingTopics() vs fetch call with browsingTopics param #344

Open
relevance-api-topics opened this issue Oct 11, 2024 · 0 comments

Comments

@relevance-api-topics
Copy link

relevance-api-topics commented Oct 11, 2024

Hi Topics API experts,

Hope to ask a question to confirm 1) document.browsingTopics() vs 2) fetch call with browsingTopics param 's functionality comparison:

  • For getting topics:
    Both 1) document.browsingTopics() and 2) fetch call with browsingTopics param get topics based on that current web-page host name is the observer.

  • For marking observer:
    Calling 1) document.browsingTopics() does not mark any observer/observation, only 2) fetch call with browsingTopics param can mark observation. And if from websiteA there is a fetch call towards websiteB, only websiteB is marked as observer based on websiteA's inferred topics, websiteA is not marked as observer for the call.

Question: if Topics API is designed as a tool supporting cookie deprecation, why when doing a fetch call from websiteA to websiteB, websiteB's observing topics cannot be filled? (for cookie case: websiteB put a cookie on websiteA, and when websiteA call websiteB the cookie websiteB setup before can be sent together)

Just to confirm above is by-design, or if we missed anything, sorry if above question is not clear enough, thanks!

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