+jsbell@ do you happen to know what could be the reason that deletion path coming from StoragePartition differs from the one in CookiesTreeModel?

Is this worth fixing in the meantime, given our plans for filesystem?

I don't have direct knowledge. I don't know if this is intentional (to preserve plugin data) or an oversight.

PluginPrivate filesystem was associated with chrome://settings/cookies dialog by following patches:
https://codereview.chromium.org/1979733002/
https://codereview.chromium.org/2359393002/

jrummel@ (author of the patches) may know if this is intentional.

My changes allowed the PluginPrivate filesystem to be cleared (in bulk using CBD or individually from the cookies dialog). Files found show up as "Media Licenses". AFAICT, the PluginPrivate filesystem is only used by Widevine. (Widevine is a hybrid component/plugin, and some day it will no longer be a plugin.)

I created a new profile, went to yahoo.com, and it doesn't appear to create a PluginPrivate filesystem (profile directory "File System/Plugins/" doesn't exist). In the cookies dialog I see 2 cookies, "Local Storage", and "File System" for www.yahoo.com. I cleared "Cookies and other site and plugin data", and afterwards the "File System" object was the only entry for yahoo.com. In fact, selecting all choices in CBD never removes the "File System" object. (www.google.com had "Database Storage", "Service Workers", and "Cache Storage" that went away when "Hosted app data" was cleared.)

So I think this bug is that "File System" objects are never removed by CBD. It's not clear to me how this object was created by a plugin.

Oh sorry, you're right. It looks like I identified the wrong problem. I still don't understand, why the "File system" entries remain. CBD calls FileSystemQuotaClient::DeleteOriginData for FileSystemTypeTemporary, syncable and persistent.

This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available. If you change it back, also remove the "Hotlist-Recharge-Cold" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

I will close this issue as I can't reproduce it anymore (Chrome 69, visit a number of sites, delete cookies for all time, check chrome://settings/siteData)