1627227 - First-party cookies are not removed when setting the preference "privacy.purge_trackers.logging.level" to "all"

Status: RESOLVED DUPLICATE of bug 1627220

(Core :: Privacy: Anti-Tracking, defect, P1)

Description

[Simona Badau, Desktop QA]

Affected versions

• Nightly 76.0a1

Affected platforms

• All

Prerequisites:

• Use a new profile.

• In about:config set the preferences
  -- privacy.purge_trackers.enabled=true.
  -- privacy.purge_trackers.logging.level =all.
  -- privacy.userInteraction.expiration =1

Steps to reproduce

1. Launch Firefox
2. Navigate to one or two popular websites to create some cookies and site storage
   (interacted with Instagram, Facebook, YouTube, Reddit)
3. Close all the tabs opened in step 2
4. Go to about:preferences#privacy and observe the cookies from the "Manage Cookies and Site Data" dialog.
5. Open the Browser Console and to send the 30 days passed interaction timeout manually, type and enter:
   await Components.classes["@mozilla.org/purge-tracker-service;1"].getService(Components.interfaces.nsIPurgeTrackerService).purgeTrackingCookieJars()
6. Check again the cookies from the "Manage Cookies and Site Data" dialog.

Expected result

• in step 6 - only the first-party cookies from the Disconnect Tracking Protection list should be removed.

Actual result

• in step 6 - the first-party cookies from the Disconnect Tracking Protection list are not removed. Instead, a third-party cookie is removed - doubleclick.net
  For more details, please look at the screencast:
  https://drive.google.com/file/d/1Nm0SuYA7GHaQeFI5BAcW9XmYubqdghc-/view

Comment 1

[Steven Englehardt [:englehardt]]

I believe the lack of clearing cookies that have received user interaction is a result of the same bug as in Bug 1627220. The purgeTrackingCookieJars() should clear both cookies that have expired user interaction and those that haven't been interacted with at all.

While checking into this I notice that I receive a console error when setting privacy.purge_trackers.logging.level =all.

22:51:19.021 await Components.classes["@mozilla.org/purge-tracker-service;1"].getService(Components.interfaces.nsIPurgeTrackerService).purgeTrackingCookieJars()
22:51:19.051 *** PurgeTrackerService:: Purging trackers enabled, beginning batch. PurgeTrackerService.jsm:283:16
22:51:19.051 Invalid Console.maxLogLevelPref value: all

I only seem to see the error after the first command I submit after restarting the browser.

Comment 2

[Johann Hofmann [:johannh]]

I think that the loglevel should simply be capitalized: All

It should also not be necessary to set a custom log level, the current default covers everything that's needed. We should refactor the logging a little bit in the future.

However, a wrong log level will not impact the functionality. This seems to be simply a dupe of bug 1627220 since it's following the same steps.

Comment 3

[Johann Hofmann [:johannh]]

It should also not be necessary to set a custom log level, the current default covers everything that's needed. We should refactor the logging a little bit in the future.

Note that this is wrong as of now, but I'm updating the log level to cover all logging in Nightly, at least.