See https://lwn.net/SubscriberLink/882607/05400c6c8702f2a1/
"Advertisers (and others) can request information via a JavaScript call to document.browsingTopics(), which will return zero to three Topic IDs, one for each of the previous three weeks, in a random order."
So let's limit the leaking information to zero on L3. L2 could return completely fake results or somehow modified results.
Metadata Update from @polcak: - Issue tagged with: new wrapper
https://groups.google.com/a/chromium.org/g/blink-dev/c/_R85yctz4Rs
Intent to Deprecate and Remove: Topics API
Explainer
https://github.com/patcg-individual-drafts/topics
Specification
https://patcg-individual-drafts.github.io/topics/
Summary
The Topics API is a privacy-preserving web API to enable ad-targeting based on a person’s general browsing interests, without exposing their exact browsing history.
Following Chrome's announcement that the current approach to third-party cookies will be maintained, we are now planning to deprecate and remove the Topics API (along with other Privacy Sandbox APIs).
==========================
Summary for JShelter:
Chrome is removing the API and is in the process of deprecation. I do not see a reason to implement the API in JShelter.
Metadata Update from @polcak: - Issue close_status updated to: Insufficient Data - Issue status updated to: Closed (was: Open)