Affected versions

• Nightly 77.0a1

Affected platforms

• All

Prerequisites:

• Use a new profile.

• In about:config set the preferences
  -- privacy.userInteraction.expiration =1.

• Make sure that in the Settings of the Web Console, "Enabled browser chrome and add-on debugging toolboxes" is checked.

• restart Firefox.

Steps to reproduce

1. Launch Firefox
2. Navigate to YouTube and play one video
3. Close the tab opened in the previous step
4. Go to about:preferences#privacy and observe the cookies from the "Manage Cookies and Site Data" dialog.
5. Open the browser console and run the following snippet:

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 5 - site data "www.youtube.com" should be purged.

Actual result

• in step 5 - site data "www.youtube.com" is not purged.

Additional notes

• if after step 6, I run again the snippet from step 5, then the site data "www.youtube.com" is deleted.
• But, if after step 6, I close the browser and open it again and then I run the snippet from step 5, the site data "www.youtube.com" is not deleted.

This only affects youtube, right? Are there any sites where this happens (would be interesting to find a pattern, maybe).

(In reply to Johann Hofmann [:johannh] from comment #1)

This only affects youtube, right? Are there any sites where this happens (would be interesting to find a pattern, maybe).

I'm also seeing this reproducing on reddit.com (64 KB here also).

This is not specific to purging, it always seems to occur when clearing data (i.e. also manually through the site data manager). Moving to data sanitization and I'll keep investigating, but I don't think this needs to block purging.

I found one scenario in which I reproduced the issue of not clearing storage residue on other sites too and the storage is also different, these are the site storage not purged: www.aol.com (273KB), www.facebook.com (160 KB), www.instagram.com (124KB), www. youtube.com (151 KB), www.google.com (48.1 KB), s.ying.com (299 bytes), opus.analytics.yahoo.com (107 bytes), accounts.google.com (7 bytes), www.ibm.com (1.2MB)

Since Bug 1633756 was marked as a dupe of this one, I must say that I've also seen other Cookies that as Yahoo.com were not purged. I'm referring to: google.com, accounts.google.com, instagram.com, pinterest.com, reddit.com, www.yahoo.com, analytics.yahoo.com, youtube.com, aol.com.

The profile where I reproduced the 2 mentioned issues is an old profile. This means that I only set the preference "privacy.userInteraction.expiration" to 1 after the cookies were generated (the preference "privacy.purge_trackers.enabled" was set to true from the beginning since I created the profile on Firefox 77 beta 7).

Steven, Johann, is it expected for the mentioned above cookies and site data not to be purged if the preference "privacy.userInteraction.expiration" is set to 1 only after the cookies are created?

The steps that I used are:

1. Open Firefox 77 beta 7 with a new profile
2. Navigate to several websites to create some cookies and site data (YouTube, Reddit, Aol, Yahoo, Google, Instagram, Pinterest, Facebook ).
3. Close Firefox, go to the location of the profile, copy the profile to your Desktop
4. Using the profile manager, create a new profile -> Create Profile -> Next -> named the profile and I chose the previously saved profile -> Finish -> Start Firefox
5. Go to about:config and set the preference "privacy.userInteraction.expiration" to 1
6. Restart firefox
7. Open the browser console and run the snippet 'await Components.classes["@mozilla.org/purge-tracker-service;1"].getService(Components.interfaces.nsIPurgeTrackerService).purgeTrackingCookieJars()'
8. Check the "Manage Data" dialog.

Steven, Johann, is it expected for the mentioned above cookies and site data not to be purged if the preference "privacy.userInteraction.expiration" is set to 1 only after the cookies are created?

Yes

What happens to all these residues? Am I going to end-up with 1GB of residue in some months? What if I re-visit the same site?

The severity field for this bug is relatively low, S3. However, the bug has 3 duplicates.
:pbz, could you consider increasing the bug severity?

For more information, please visit auto_nag documentation.

I can't reproduce this issue or its duplicates. If I remove data for a site, e.g. YouTube or Facebook it will not re-appear in the data clearing window. After clearing all site-data and restarting Firefox, there will be new data added, because about:newtab populates the cache.
Happy to reopen the bug if anybody else runs into this issue!