- Issue created by @nitesh624
This is something to help an advertising company track users.
This should be implemented in a contributed module.
- 🇮🇳India nitesh624 Ranchi, India
but our site does not have any track for used for advertisement.
By default chrome://settings/adPrivacy/interests settings is check and if I unchecked it the console error gone That is correct. It looks like Google's built-in advertising business in their Chrome browser is again making use of the permissions policy browser feature (working draft) to ask the site which topics are allowed to be advertised on the site, or something like that.
Assuming I am correct about this, Drupal Core was openly against Google's prior attempt → to do this kind of thing.
So, do we want to block this new thing also?
- 🇬🇧United Kingdom longwave UK
This header can already be managed in contrib with https://www.drupal.org/project/permissionspolicy →
- Status changed to Fixed
12 months ago 5:57pm 2 February 2024 - 🇮🇳India nitesh624 Ranchi, India
shouldn't this issue to be fixed from core instead of using contrib module?
- 🇬🇧United Kingdom longwave UK
What is the bug? Core isn't doing anything wrong, and it's up to individual sites whether they want to do anything with the Topics API.
- 🇮🇳India nitesh624 Ranchi, India
so will there be any issue, if any sites does not provide this permission-policy header?
Automatically closed - issue fixed for 2 weeks with no activity.