User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:68.0) Gecko/20100101 Firefox/68.0
Steps to reproduce:
Go to a website with trackers (e.g. heise.de), check that the console lists
Request to access cookie or storage on “<URL>” was blocked because it came from a tracker and content blocking is enabled. 28
Disable Enhanced Tracking Protection
The console shows
Request to access cookie or storage on “<URL>” was blocked because it came from a tracker and content blocking is enabled. 10. Sometimes this requires an additional reload to show up. Note that the number of blocked trackers is less than with EPT, this is consistent.
I ran mozregression which narrowed the behavior down to this commit: https://phabricator.services.mozilla.com/D68189 (Change isOnContentBlockingAllowList in storageAccessAPIHelpers.js to use allowListed flag instead of permission.)
All mozregression settings besides the page to load on startup were left on default.
Apparently some trackers are still blocked even when the site is excluded. I’ve had it happen, that some files for Google Ads did not load.
All trackers and ads are allowed.