Maybe some Google Chrome entries can be found on the chrome add-on Click&Clean v7.9. I don't know how but it is maybe not too complicated.
qsdewa, please don't link to competitors if that's what that is.
you'd be better served by telling us what is "some entries" tell us what you think needs additional cleaning.
also please see my private message.
qsdewa, please don't link to competitors if that's what that is.
you'd be better served by telling us what is "some entries" tell us what you think needs additional cleaning.
also please see my private message.
Ok. I meant for example "Web Local Storages" and "Sandoxed Filesystem" which can be found in the options menu of Click&Clean (and yes, it seems to be a competitor). I do not know what the entries could be, because I tried to figure out some things (removing folders for example \AppData\Local\Chromium\User Data\Default\Local Storage) but it only broke my extenion settings and so in Chrome. So I hoped someone knows something.
I believe local storage is covered by Chrome Cookies in ccleaner
Click&Clean I would see as a competitor to CCleaner, so good call Nergal.
______________________
Although not Chrome, but based upon it, this is what I clean in Dragon. Don't know what in this cleaner would work in Chrome though:
[Comodo Dragon (More)]
LangSecRef=3029
Detect=HKLM\Software\ComodoGroup\Dragon
Default=False
FileKey1=%LocalAppData%\COMODO|.lock|RECURSE
FileKey2=%LocalAppData%\COMODO\Dragon\User Data\Default|Bookmarks.bak
FileKey3=%LocalAppData%\COMODO\Dragon\User Data\Default|Extension Cookies
FileKey4=%LocalAppData%\COMODO\Dragon\User Data\Default|Network Action Predictor-journal
FileKey5=%LocalAppData%\COMODO\Dragon\User Data\Default\Media Cache|.|RECURSE
FileKey6=%LocalAppData%\COMODO\Dragon\User Data\Default\Temp|.|RECURSE
And that's about all I'm comfortable cleaning in it using this "(More)" entry, as I don't know what would or wouldn't break something.
winapp2.ini covers a bit more on the chrome front, if that's any help
Yeah, but only if so many of those cleaners weren't all jammed together, i.e.; some separation for per browser name individuality would be welcome.